Skip to content
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

Fix node-20, reenable node-latest in CI #738

Closed
ssalbdivad opened this issue Apr 30, 2023 · 0 comments
Closed

Fix node-20, reenable node-latest in CI #738

ssalbdivad opened this issue Apr 30, 2023 · 0 comments

Comments

@ssalbdivad
Copy link
Member

ssalbdivad commented Apr 30, 2023

Currently I'm unable to find a reasonable solution for using ts-node (or others like tsx)/ts-morph reliably with Node 20.

I believe it was related to a breaking change with how subprocesses are spawned, but ts-morph constantly hangs when running attest, and when trying to use vscode's builtin debugger, more and more processes are continuously spawned, e.g. :

Image

Source maps also appear to be broken on Node 20.

Related:

TypeStrong/ts-node#1997

Would love if someone could take a look at this but unfortunately I've spent too long on it and the current plan is to wait until Node 20 stabilizes a bit as it's basically just broken everything I've tried it with.

Once these issues are resolved, CI can be reenabled here:

node: latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done (merged or closed)
Development

No branches or pull requests

1 participant