esbuild-wasm is now erroring out from missing builtin node packages on the web

[okikio]

esbuild-wasm uses "fs", "crypto", etc... in the source code, but those packages can't be bundled and sent to the web so trying to use bundle esbuild-wasm for the web keeps failing, this specifically only occurs in versions >=v0.14.26 that includes the latest version as of this post v0.14.27.

You can replicate this issue here: https://stackblitz.com/github/okikio/bundle/tree/012f041ef099b6d9e734654adb2d7f8d4744aa2d?file=package.json

# Run 
npm run build

The error should appear.

[hyrious]

This might be a regression of #2081 that moves code including require("fs") from a string (will be evaluated by Function()) to outside.

We can try to wrap these code in a try-catch so that esbuild won't complain about these require calls.

[okikio]

I hope that the problem is fixed

[evanw]

I believe this was accidentally fixed by me upgrading to Go 1.18.0, which separated out node-related stuff into another file: golang/go@680caf1. So this should be fixed in the upcoming release of esbuild.

[okikio]

Awesome