-
Notifications
You must be signed in to change notification settings - Fork 383
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
NodeJS LTS 20 Support #5989
Labels
Comments
Yeah, this is a duplicate of #5910. Github has been switching over slowly today and jobs have been intermittently failing. I think I have something that should work, but need to make sure it works on both 18 and 20. I'm going to close this as a duplicate of that other issue. |
quisquous
added a commit
that referenced
this issue
Dec 20, 2023
Instead of: `ts-node util/sync_files.ts` Now we must do: `node --loader=ts-node/esm util/sync_files.ts` This should work on both node 18 and node 20 (tested locally). Git workflows were pinned to 18.18.2 via #5991, but are now updated to 20 for constency. It's possible that ts-node will fix this in the future and we can remove (again) the loader param. Fixes #5910. Fixes #5989.
github-actions bot
pushed a commit
that referenced
this issue
Dec 20, 2023
Instead of: `ts-node util/sync_files.ts` Now we must do: `node --loader=ts-node/esm util/sync_files.ts` This should work on both node 18 and node 20 (tested locally). Git workflows were pinned to 18.18.2 via #5991, but are now updated to 20 for constency. It's possible that ts-node will fix this in the future and we can remove (again) the loader param. Fixes #5910. Fixes #5989. 4c5cf21
github-actions bot
pushed a commit
that referenced
this issue
Dec 20, 2023
Instead of: `ts-node util/sync_files.ts` Now we must do: `node --loader=ts-node/esm util/sync_files.ts` This should work on both node 18 and node 20 (tested locally). Git workflows were pinned to 18.18.2 via #5991, but are now updated to 20 for constency. It's possible that ts-node will fix this in the future and we can remove (again) the loader param. Fixes #5910. Fixes #5989. 4c5cf21
github-actions bot
pushed a commit
to SiliconExarch/cactbot
that referenced
this issue
Jan 5, 2024
…quous#5990) Instead of: `ts-node util/sync_files.ts` Now we must do: `node --loader=ts-node/esm util/sync_files.ts` This should work on both node 18 and node 20 (tested locally). Git workflows were pinned to 18.18.2 via quisquous#5991, but are now updated to 20 for constency. It's possible that ts-node will fix this in the future and we can remove (again) the loader param. Fixes quisquous#5910. Fixes quisquous#5989. 4c5cf21
github-actions bot
pushed a commit
to SiliconExarch/cactbot
that referenced
this issue
Jan 6, 2024
…quous#5990) Instead of: `ts-node util/sync_files.ts` Now we must do: `node --loader=ts-node/esm util/sync_files.ts` This should work on both node 18 and node 20 (tested locally). Git workflows were pinned to 18.18.2 via quisquous#5991, but are now updated to 20 for constency. It's possible that ts-node will fix this in the future and we can remove (again) the loader param. Fixes quisquous#5910. Fixes quisquous#5989. 4c5cf21
github-actions bot
pushed a commit
to SiliconExarch/cactbot
that referenced
this issue
Jan 6, 2024
…quous#5990) Instead of: `ts-node util/sync_files.ts` Now we must do: `node --loader=ts-node/esm util/sync_files.ts` This should work on both node 18 and node 20 (tested locally). Git workflows were pinned to 18.18.2 via quisquous#5991, but are now updated to 20 for constency. It's possible that ts-node will fix this in the future and we can remove (again) the loader param. Fixes quisquous#5910. Fixes quisquous#5989. 4c5cf21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NodeJS 18 LTS ended active support over a month ago although it still is receiving security updates. Node is pushing 20 LTS now on their website and on Windows, the winget package manager is actively trying to upgrade 18 to 20.
I propose adding support for the current mainstream v20 LTS.
When trying to set things up with 20, you get the following:
The text was updated successfully, but these errors were encountered: