Open LennardF1989 opened 2 weeks ago
Did some additional testing:
Here is a list of changes: https://github.com/privatenumber/tsx/compare/v4.8.2..v4.9.0
It probably has to do with something not properly cleaning up after closing the last node process.
I added a test.js to the 4.9.0 StackBlitz (node test.js
) and it will not even reach the console.log('Start!');
before the tsx-import.
Compared to node index.js
followed by a ps
shows no node process, while after running tsx index.ts
, it does after which all node-process "stick". They also cannot be killed.
Describe the bug
Using tsx causes the node process to hang when running it for a second time inside a WebContainer. This does not happen on an actual machine.
Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-webcontainer-api-starter-8mpkbw?file=index.js,index.ts,package.json
package.json
index.js/index.ts
Steps to reproduce
npm run test-1
multiple times, there is no issue.npm run test-2
multiple times, either the second or the third time it will hang and no longer respond anymore.Open a new terminal, run
ps
and kill one of the latestnode
processes usingkill -9 PID
- the other terminal will go responsive again.Expected behavior
test-2 behaves in the same way as test-1.
Parity with Local
Screenshots
No response
Platform
Additional context
No response