esbuild-plugin-global-externals VS esbuild-plugin-prismjs

The only thing that tripped me up was the difference between esbuild's `externals` and webpack's `externals`. In webpack you can use the externals config to skip bundling a module and instead get it from another source such as a Node module or, in my case, from a global variable in the browser. In esbuild, an external module is only for the first situation (getting a module from Node instead of bundling it), so I was confused about how I can transfer the desired behavior over to esbuild. Luckily I found a plugin that does exactly what I want: [0].

Other than that, I'm pretty darn satisfied with what esbuild can do out of the box. I don't use any other plugins except global externals, and I don't find myself missing anything from webpack. So far it's just better in every way (for myself at least).

[0]: https://github.com/fal-works/esbuild-plugin-global-externals

We have created a plugin that allows you to use the same settings when migrating from prismjs + webpack + babel to prismjs + esbuild. It's easy to use because you just need to migrate the language and plugin information set in .babelrc to the optional arguments of the new plugin. https://github.com/activeguild/esbuild-plugin-prismjs