Actually I would prefer avoid Volta since it would introduce a private field in package.json which is not used and understandable by the rest of the world.
Just imagine a better node version manager in the future. That new node version manager will have to support the Volta field even if it is not Volta.
Yet another weirdness like what we have been facing with :-).
It is the engines field. docs.volta.sh/guide/understanding#...
Actually I would prefer avoid Volta since it would introduce a private field in package.json which is not used and understandable by the rest of the world.
Weird flex, but ok.
Just imagine a better node version manager in the future. That new node version manager will have to support the Volta field even if it is not Volta.
Yet another weirdness like what we have been facing with :-).
That doesn't seem to be the engines field though.
yeah, you are correct on that. Seems like Volta explains that here. github.com/volta-cli/volta/issues/...