chore: bump Node to v20 #1084
Closed
chore: bump Node to v20 #1084
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey Kris, since this is going to be a PITA as is, do you want to try 11ty v3 and Node 22 both of which are LTS now. |
|
Oh nice, I didn't realize that v22 is LTS already. Sure thing, that sounds like a plan. Might as well rip the bandaid off on all those things 🙂 |
|
The main pain point is to migrate all the JS (11ty & related builder code) to ESM. Then on it is a smoother ride. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist:
Update index.md)This bumps Node to v20 and npm to v10 everywhere, and refreshes the
package-lock.jsonfile.