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
Thanks for your quick work on 598. I tried to run swc over our test-suite to get you some real-world testcases, but got consistent panics on several files. I reduced it to a minimal testcase which consistently panics, both with the official binaries and with npm_config_build_from_source=1, on x64 linux.
The minimal testcase is this:
asyncfunctionfoo(){for(letaofb){}}
Removing the async fixes it, removing the loop (or using a different kind of loop) fixes it.
npx swc --no-swcrc test.js
fatal runtime error: failed to initiate panic, error 5
No way to get a panic message or backtrace, unfortunately. I wish there was a cli binary that didn't go through node..
The text was updated successfully, but these errors were encountered:
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Thanks for your quick work on 598. I tried to run swc over our test-suite to get you some real-world testcases, but got consistent panics on several files. I reduced it to a minimal testcase which consistently panics, both with the official binaries and with
npm_config_build_from_source=1
, on x64 linux.The minimal testcase is this:
Removing the async fixes it, removing the loop (or using a different kind of loop) fixes it.
npx swc --no-swcrc test.js
No way to get a panic message or backtrace, unfortunately. I wish there was a cli binary that didn't go through node..
The text was updated successfully, but these errors were encountered: