-
Notifications
You must be signed in to change notification settings - Fork 384
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
Node 20 requires loader parameter again #5910
Labels
Comments
quisquous
added a commit
that referenced
this issue
Dec 6, 2023
Do this until a better solution for #5910 exists.
It looks like v18.19.0 breaks but v18.18.2 is fine, based on some failing jobs today. |
quisquous
added a commit
that referenced
this issue
Dec 6, 2023
Do this until a better solution for #5910 exists.
Hmm #5986 did not appear to do anything, so this needs to be fixed or jobs will just fail randomly if they get a too-new node version. |
Closed
quisquous
added a commit
that referenced
this issue
Dec 7, 2023
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
See conversation thread here: #5859 (comment)
With Node 18 this works, but with Node 20 it seems to revert to previous behavior.
The text was updated successfully, but these errors were encountered: