Closed rahulrana701 closed 4 months ago
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.
Hi @lindapaiste I would like to work on this issue so please assign it to me
I'm not familiar with Volta at all but this sounds fine to me. Like there's no major downside to having extra info in the package.json
. It's weird that Volta can't just use the engines
which is a standard property that we already have set.
You should add a section to the contributor documentation explaining how to use Volta with this project.
@lindapaiste done
Thanks for suggesting this! After reading about Volta, although it does sound great and might bring some additional benefits, I personally don't feel like there's a strong need to add this yet, especially since it's much newer compared to nvm
, which has been around for a while.
I definitely think it would be great to reconsider switching to Volta down the line after it gets some more usage, or seeing what other options also pop up!
Increasing Access
Via using this tool that is volta we don't have to update the node version's using nvm we just have to install volta once and then according to the version of node and npm a particular project is using it will adjust accordingly , we don't have to use nvm to update the versions. Using Volta is a better approach
Feature request details
I have added a volta script in package.json in this way whosoever have volta installed locally they don't have to update their node versions to specific version , they just have to clone the repo and
start working on it as volta will take care of the versions of npm and node