search

GoogleChromeLabs / tooling.report

tooling.report a quick way to determine the best build tool for your next web project, or if tooling migration is worth it, or how to adopt a tool's best practice into your existing configuration and code base.
https://tooling.report
Apache License 2.0
848 stars 49 forks source link

[Meta] Prioritization of next bundlers #232

Open surma opened 4 years ago

surma commented 4 years ago

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.

osdevisnot commented 3 years ago

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.

bjesuiter commented 3 years ago

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.

nicod-pc commented 3 years ago

According to State of JS 2020 there is a high interest on Snowpack and esbuild: https://2020.stateofjs.com/en-US/technologies/build-tools/