You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team use different tool to manage node version.
I like volta!
How to use a specific version without add "volta": {} to package.json?
Currently, I pin and delete volta part from package.json.
and something like below live in root package.json
"engines": {
"node": "12 || 14"
}
The text was updated successfully, but these errors were encountered:
Hi @keidarcy! Unfortunately, we don't currently support any other method for pinning the Node version. There's an open issue (that needs some design work to be implementable) tracking the idea of using a separate file to pin the versions: #282
Note that deleting the volta entry from package.json will make Volta use the global defaults (as the package doesn't have any Volta configuration). The only thing that volta pin does (other than cache the requested version locally) is to write that entry, so removing it is effectively undoing volta pin.
As for engines, we actually looked early on at using it, and decided against it, for reasons outlined in this comment: #742 (comment)
My team use different tool to manage node version.
I like volta!
How to use a specific version without add "volta": {} to
package.json
?Currently, I pin and delete
volta
part frompackage.json
.and something like below live in root
package.json
The text was updated successfully, but these errors were encountered: