Live data from Hacker News

Some notes on using esbuild

jvns.ca

1–10 of 205 posts

Re: Some notes on using esbuild

#2
Esbuild is great. We couldn't fully migrate to esbuild due to some hard dependencies on webpack but we are currently using esbuild-loader which reduced our build times considerably.

Re: Some notes on using esbuild

#3
post #2

Esbuild is great. We couldn't fully migrate to esbuild due to some hard dependencies on webpack but we are currently using esbuild-loader which reduced our build times considerably.

You can also use the esbuild terser backend for minification. Almost halved the time of our release build

Re: Some notes on using esbuild

#5
If you want to keep things simple while using packaged libs, there's no need for a build step. You can import ES Modules directly in a script by using URL as module name. Use e. g. ESM.sh as the registry, most NPM packages are available.

Re: Some notes on using esbuild

#7
Julia is one of my favorite examples of learning in public as a developer. Her technical chops are unquestioned so when she says things like "I have no idea what import does" it really drives home how much the JS community has to do to bring along the rest of the developer population who just wants to make web stuff occasionally without going to JS Build Tool University.

I love this and maybe it would be great for someone who works on the spec/bundlers to write a "Dear Julia" letter explaining things and giving context to specific parts on why things are the way they are, and pointing out clear ways that we as a community should try to improve.

Re: Some notes on using esbuild

#10
post #5

If you want to keep things simple while using packaged libs, there's no need for a build step. You can import ES Modules directly in a script by using URL as module name. Use e. g. ESM.sh as the registry, most NPM packages are available.

this does not fulfill the requirement of her: 'I could fix them when they break'
Post reply on HN