2 months ago
pnpm builds that have previously deployed are now failing to build (doing a re-deploy)
```
pnpm add -g node-gyp
1s
[ERROR] The configured global bin directory "/pnpm/bin" is not in PATH
Run "pnpm setup" to update your shell configuration.
copy /root/.local/state/mise, /etc/mise/config.toml, /usr/local/bin/mise, /mise/installs, /mise/shims cached
0ms
Build Failed: build daemon returned an error < failed to solve: process "pnpm add -g node-gyp" did not complete successfully: exit code: 1 >
```
Pinned Solution
2 months ago
Hello, I recently had a similar error message on Docker. After investigating, we found that the issue was that the pnpm version wasn’t fixed in our Dockerfile, and our workflow wasn’t compatible with the recently released pnpm 11. We pinned pnpm to an older version, and everything started working again. Hope it helps!
6 Replies
Status changed to Open Railway • 2 months ago
2 months ago
If you don't need node-gyp installed globally, you can install it as a dev dependency to bypass this error. Change your pnpm add command to: pnpm add -D node-gyp
2 months ago
it's railpack that is running the command, not something i am running myself in the build process. I believe it's a dependency of argon2
2 months ago
It builds fine on nixpacks, not on railpack
dane-stevens
It builds fine on nixpacks, not on railpack
2 months ago
Nixpacks is deprecated. It's not recommended to use it anymore. You can however switch to a Dockerfile setup, and you won't have this issue with Railpack.
2 months ago
My issue is that the same build deployed yesterday on railpack and today it's failing trying to redeploy.
2 months ago
Hello, I recently had a similar error message on Docker. After investigating, we found that the issue was that the pnpm version wasn’t fixed in our Dockerfile, and our workflow wasn’t compatible with the recently released pnpm 11. We pinned pnpm to an older version, and everything started working again. Hope it helps!
Status changed to Solved chandrika • about 1 month ago