Open shinokada opened 3 months ago
Hi @shinokada, thanks for the suggestion! I think migrating is a bit tricky so adding a page on how to do so is potentially difficult. Both Volta and nvm work in roughly the same space, but they also have very different mental models on how tools are managed.
Additionally, nvm has a variety of different configurations / additions that can change how it's used, which complicates the migration since it might not work with every use-case.
Lastly, we would ideally want to make things more generic, rather than calling out nvm specifically. nvm is a great tool that we've used in the past, and while the Volta maintainers understandably prefer Volta for managing tool versions, our philosophy has generally been to avoid comparisons with other tools and rather to focus on Volta's benefits. For a "migration" doc, I wonder if it would be unreasonable to write it in a way that is general across various other methods (e.g. calling out that the version needs to be pinned in package.json
instead of another file, plus making sure Volta is first on the PATH
).
I currently use nvm for node version manager on macOS which is installed by brew. Is it possible to add a migration page on https://docs.volta.sh/guide/getting-started on how to migrate from nvm to Volta?