Open justinfagnani opened 3 years ago
I think that's a fair question. esbuild is still a pretty new tool, so when I added it it was more experimental and naming it explicitly made sense. We do require the user to install the @web/dev-server-esbuild
plugin when using this flag, to avoid users from installing it when they don't need it, but I could see that naming the option es-target
makes sense.
Is there a reason "esbuild" needs to be in the name? That ties this option to esbuild, which would ideally be more of an implementation detail, at least from the builtin flags. Why not something like
js-target
?