You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
merceyz
changed the title
esbuild-wasm@0.15.14 closes with no output and exit code 130 on Node.js v19esbuild-wasm@0.15.14 closes with no output and exit code 130 with Node.js v19
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:
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
The text was updated successfully, but these errors were encountered: