3 ms·
My own fix for the node version issue is that we use a single version of nodejs (currently latest v12), and when we update, we update everything (which happens
by forty 5y ago
My own fix for the node version issue is that we use a single version of nodejs (currently latest v12), and when we update, we update everything (which happens every two years, and is generally not too painful in my experience), so we just have to have this version locally.
- tqkxzugoaupvwqr 5y agonvm (node version manager) is your friend. Allows you to use different node versions for different projects.
- scns 5y agohttps://volta.sh https://volta.sh too
- forty 5y agoI used to use nvm, nave, n and similar things, but I think having a single version of node for all projects is easier and better. I just have unattended upgrade setup everywhere, so I have always the latest v12 without having to think about it.
- nucleardog 5y agoYes, it's do-able. As others have pointed out, nvm also works. 1. There isn't nvm for things that aren't node. Some things have an equivalent (e.g., pyenv). Many external dependencies do not. 2. I've inherited a spiderweb of like two dozen different major projects that are all interconnected. Doing an upgrade across everything at once means a stop-work for months while all the developers update tooling, then fix all their issues so everything works, then we try and coordinate testing and deploys of everything without breaking anything. Or, alternatively: 1. We don't need extra tooling that doesn't exist. 2. We can update projects one at a time instead of mass-migrating several million lines of code across half a dozen different frameworks.