Contribution
Describe the user story
All projects in monorepo should be able to define own version of node to use in package.json.
Describe the solution you'd like
engines already allow defining range of node versions for project. pnpm env use can already download node version, so it should download newest node version that satisfy range for that project.
scripts that pnpm runs will automatically use correct node version for that script.
Describe the drawbacks of your solution
Takes time to download node when you want to run command the first time. There can be command to download all node versions for project like pnpm env downloadAll ./repo which will download all node version needed in all project in the repo which you can run when downloading repo for first time.
Describe alternatives you've considered
Manually manage node versions for all projects but is complicated.
Contribution
Describe the user story
All projects in monorepo should be able to define own version of node to use in package.json.
Describe the solution you'd like
enginesalready allow defining range of node versions for project.pnpm env usecan already download node version, so it should download newest node version that satisfy range for that project.scriptsthat pnpm runs will automatically use correct node version for that script.Describe the drawbacks of your solution
Takes time to download node when you want to run command the first time. There can be command to download all node versions for project like
pnpm env downloadAll ./repowhich will download all node version needed in all project in the repo which you can run when downloading repo for first time.Describe alternatives you've considered
Manually manage node versions for all projects but is complicated.