You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the Github Project, it seems closure compiler is next on priority. However based on stats on npmtrends, it seems esbuild is quickly becoming a popular bundler in JS/TS tooling space. These stats however might not be authoritative since closure compiler can be used multiple ways, eg: outside npm and behind private proxies, etc. Another reason to prioritize esbuild is it's support for TS source code without any external dependency.
Would love to hear team's thought on such prioritization. I am also looking forward to contributing the feature if we agree on prioritization.
Maybe you want to include Snowpack after version v3?
I think, it is a better comparison in terms of build system tooling to rollup and webpack, compared with esbuild.
And Snowpack uses esbuild under the hood, so, for me, esbuild seems more like a 'compiler' or 'bundler' instead as a whole build system.
We now have a GitHub Project to organize which bundlers should get added next.
The order in that board roughly represents our priorities.
This issue is should be used to discuss said prioritization.
The text was updated successfully, but these errors were encountered: