-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
deno_emit fails depending on whether or not a breakpoint is set. #15015
Comments
Same issue is reported over at denoland/vscode_deno#708 and I'm seeing the same when attempting to debug in IntelliJ. All good until the code transitions into some WASM, then we get the error above and execution terminates. |
Having the same issue. deno_emit import fails with error Uncaught (in promise) TypeError: WebAssembly.compile(): Argument 0 must be a buffer source when launching in vs code. Is there still no cure for this? |
The same thing appears to happen with the bundle function, and indeed using IntelliJ only occurs when debugging, if running without debugging the output appears to be alright, so it does appear to have to do with the --inspect-brk option. |
I am also having the same issue when using If I use the current default launch config shown below which uses "version": "0.2.0",
"configurations": [
{
"request": "launch",
"name": "Launch Program",
"type": "node",
"program": "${workspaceFolder}/main.ts",
"cwd": "${workspaceFolder}",
"runtimeExecutable": "C:\\Users\\kinso\\.deno\\bin\\deno.EXE",
"runtimeArgs": [
"run",
"--inspect-wait",
"--allow-all"
],
"attachSimplePort": 9229
}
] But if I just execute the script using the deno CLI, everything works fine. |
Not sure if this is a Deno issue, or a deno_emit issue, but it seems like debugging shouldn't affect the code like this so I'm assuming this is an issue with Deno.
To reproduce:
emit.js
deno run -A --unstable --inspect-brk emit.js
console.log
line.Actual result
Uncaught (in promise) TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
Expected result
The code runs without any errors.
Some things to note:
--inspect-brk
make the code run like normal.The text was updated successfully, but these errors were encountered: