[Important PR~not to merge without deployment plan] Upgrade to Node 20 #474
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.
resolve #441
I did a pretty exhaustive look through our repos, and as far as I can tell, I actually don't think upgrading
node
will change so much stuff!I changed the version here in
setup
. Then, infullstack-challenges
, I added an.nvmrc
file for those with it set up to change their version withnvm
automatically. And I did the same infullstack-solutions
and then went into every single challenge in the JS units and ranrake
to make sure they still raked green, ranserve
to check the result myself, and raneslint --fix *
to improve the style.But, given that the students really never use
node
during the challenges, I actually don't think this should affect much. And, we don't usenode
in Rails anymore, so I don't think it should affect any of the rails lectures or any of our Rails-related repos, agreed?I feel like there should be more to do or something...but I think this is actually everything?
related: