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
This is a family of highly related bugs, and the two links are for two different sets of test cases. Here's the expectation with each type of bug:
Invalid to invalid: process to remain alive and print resulting error
Valid to invalid: process to remain alive and print resulting error
Invalid to valid: dist.js to be created/updated
Actual Behavior
Invalid to invalid: process crashes, silently in Node 16 but with output in Node 20
Valid to invalid: process crashes, silently in Node 16 but with output in Node 20
Invalid to valid: dist.js is not generated, even if you touch it after the initial correction
The error generated by Node v20.1.0 is this:
node:internal/errors:490
ErrorCaptureStackTrace(err);
^
TypeError [ERR_INVALID_ARG_TYPE]: The "code" argument must be of type number. Received an instance of Error
at process.set [as exitCode] (node:internal/bootstrap/node:124:9)
at process.exit (node:internal/process/per_thread:188:24)
at process.close (/home/claudia/rollup-typescript-silent-crash/node_modules/rollup/dist/shared/watch-cli.js:543:19) {
code: 'ERR_INVALID_ARG_TYPE'
}
The README details each one of these in full.
Additional Information
Here's what I tried:
Installing with clean npm caches using --cache
Restarting the Debian VM in WSL, to check for kernel state issues
Creating a new throwaway Ubuntu VM in WSL, to fully isolate the kernel's state
The issue in question is a family of highly related errors. The reason they're split is because I did a few times have the type variant (but not the unused variant) report an actual TS error before exiting, but I wasn't able to easily isolate it while putting together this repro. I also suspect it's just a minor variation of the same issue.
Let me know if you need anything else.
The text was updated successfully, but these errors were encountered:
Filed rollup/rollup#4986 to track it on Rollup's side, in case it's a Rollup proper issue (which I find most likely). Still filed it here as well since I couldn't fully isolate it from the TypeScript plugin.
Hey folks. This issue hasn't received any traction for 60 days, so we're going to close this for housekeeping. If this is still an ongoing issue, please do consider contributing a Pull Request to resolve it. Further discussion is always welcome even with the issue closed. If anything actionable is posted in the comments, we'll consider reopening it. ⓘ
Expected Behavior
This is a family of highly related bugs, and the two links are for two different sets of test cases. Here's the expectation with each type of bug:
dist.js
to be created/updatedActual Behavior
dist.js
is not generated, even if youtouch
it after the initial correctionThe error generated by Node v20.1.0 is this:
The README details each one of these in full.
Additional Information
Here's what I tried:
npm
caches using--cache
The issue in question is a family of highly related errors. The reason they're split is because I did a few times have the type variant (but not the unused variant) report an actual TS error before exiting, but I wasn't able to easily isolate it while putting together this repro. I also suspect it's just a minor variation of the same issue.
Let me know if you need anything else.
The text was updated successfully, but these errors were encountered: