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
Executing it only prints before and then exits with code 13.
I don't know where the exit code is set, but it seems that we actually detect that the promise representing the module's execution never settles.
Could we emit/print a warning when it happens? Ideally it could contain the path to the problematic module.
The text was updated successfully, but these errors were encountered:
targos
added
esm
Issues and PRs related to the ECMAScript Modules implementation.
errors
Issues and PRs related to JavaScript errors originated in Node.js core.
labels
Aug 5, 2021
I was confused to notice a failing command when I switched shells, even though my Node program wasn't printing any errors. I had to do a few minutes of searching to understand what was going on. An error explaining how this can be fixed would be helpful.
Here's a simple ES module with top-level await:
Executing it only prints
before
and then exits with code13
.I don't know where the exit code is set, but it seems that we actually detect that the promise representing the module's execution never settles.
Could we emit/print a warning when it happens? Ideally it could contain the path to the problematic module.
The text was updated successfully, but these errors were encountered: