Closed ajdubovoy closed 1 month ago
👋 @ajdubovoy, indeed it should be pretty safe to upgrade w/o disrupting challenges / solutions. That said, have you checked
❓
Taking a look now:
importmap
branch?importmap
(yay) but for some reason has an empty node_modules/
directory committed. Not really important but maybe we should delete that?node_modules/
is there but not usedopened prs for this
All of those seemed super tiny to me and unlikely to cause issues!
FYI also, unrelated but similar. I've started going through repos one by one and opening prs to move to the latest version of Ruby. I'll make a big pr in setup and link to alllllll the prs in the other repos once I'm done, so don't worry about checking those prs individually at the moment
@Eschults ok if I merge this one as well?
🚀
resolve https://github.com/lewagon/setup/issues/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: