Describe the bug
The documentation says that we can set the PNPM_VERSION env var to control which pnpm version is installed during the heroku build.
However, when we set the engines.pnpm in the package.json, the buildpack is using that value over the env var which is not what I'd expect reading the documentation.
For us, this is not a big deal, it was just surprising. I'm also not sure this was an intentional change or just a coincidence. Probably it's worth documenting and/or fixing.
I think this commit introduced this new behaviour.
To Reproduce
Steps to reproduce the behavior:
Set the pnpm version in the package.json like this:
"engines": {
"node": "16.x",
"pnpm": "8.x"
}
Set the PNPM_VERSION env var in your Heroku app to 7.30.5
Build your app
See that the buildpack is installing pnpm 8.2.0
Versions (please complete the following information):
Heroku Stack: heroku-22
Node Version: 16.20.0
NPM or Yarn Version: NPM 8.19.4
Buildpack Version: latest
Additional context
Add any other context about the problem here.
Describe the bug The documentation says that we can set the PNPM_VERSION env var to control which pnpm version is installed during the heroku build. However, when we set the engines.pnpm in the package.json, the buildpack is using that value over the env var which is not what I'd expect reading the documentation. For us, this is not a big deal, it was just surprising. I'm also not sure this was an intentional change or just a coincidence. Probably it's worth documenting and/or fixing. I think this commit introduced this new behaviour.
To Reproduce Steps to reproduce the behavior:
Versions (please complete the following information):
heroku-2216.20.0NPM 8.19.4latestAdditional context Add any other context about the problem here.