Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

esbuild-wasm@0.15.14 closes with no output and exit code 130 with Node.js v19 #2683

Closed
merceyz opened this issue Nov 19, 2022 · 1 comment
Closed

Comments

@merceyz
Copy link

merceyz commented Nov 19, 2022

Describe the bug

Running esbuild-wasm@0.15.14 with Node.js v19 closes without any output and exit code 130.

Ref nodejs/citgm#905 (comment)

To Reproduce

docker run --rm -it node:19.1.0 bash
cd $(mktemp -d)
yarn init -2
yarn config set nodeLinker node-modules
yarn add esbuild-wasm@0.15.14
yarn esbuild --help
echo $?
@merceyz merceyz changed the title esbuild-wasm@0.15.14 closes with no output and exit code 130 on Node.js v19 esbuild-wasm@0.15.14 closes with no output and exit code 130 with Node.js v19 Nov 20, 2022
@evanw
Copy link
Owner

evanw commented Nov 20, 2022

Thanks for the report. I can reproduce this. Here is the specific error that happens:

globalThis.crypto = {
                  ^

TypeError: Cannot set property crypto of #<Object> which has only a getter

This problem doesn't happen in esbuild's code. It looks like this error is an unfortunate interaction between Go's WebAssembly shim code and some recent changes made by Node v19:

I'll see what I can do about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants