tsconfig-paths-webpack-plugin VS wmr

You can see an example of such resolver here: https://github.com/dividab/tsconfig-paths-webpack-plugin/blob/master/src/plugin.ts

We already have configured path aliases with webpack and tsconfig - so I wanted to keep that behavior. Luckily we have the vite-tsconfig-paths exactly for that. It worked well. I could also try using the alias for that.

wmr for near-instant builds & native TS support

Preferred tech stack is always something I choose for the job at hand. That might just be a few rollup plugins + a tool like WMR or Vite, but it can be also be quite complex and custom build system too. It depends.

While the development process is evolving for developers, there’s a need by many developers to have an all-in-one development tool that will make web application development faster and easier. WMR gives developers the added feature and advantage of building web applications based on the all-in-one development tool.

wmr does not have error overlay / SVGR support

It did not take a lot of time to choose the tool. Currently, there are 3 major bundlers powered by ESM - vite, snowpack, and wmr. From the first glance - all of them look promising and I did not care about their internals as long as I don't need to touch them.

WMR could be another option if you haven’t already seen it.

wmr is an all-in-one development tool for modern web apps. Since it leverages ESM modules, it only requires an HTML files with

Thanks! I'll watch this today on lunch break. :) To be frank, I'm not even a Vue user, but Vite looks truly awesome. I love that popular framework authors are taking the time to make their build tools framework-agnostic (also see, wmr by the Preact guys).