Closed tom-quiltt closed 1 year ago
FWIW we had the buildpack pinned to 76cf1fc and it also started showing the pnpm: command not found
error mentioned above. it might be that something in the Heroku machines has changed that makes this not work anymore.
I forked this build pack and modify it in https://github.com/unfold/heroku-buildpack-pnpm/pull/40, and it works for me. Let me know if there's anything I can help with.
Hello ! seems to be an issue with unpkg
https://github.com/mjackson/unpkg/issues/361
Proposed fix: https://github.com/mjackson/unpkg/issues/358#issuecomment-1496263654
Describe the bug With the new version of buildpack, the script to respect
engines.pnpm
seems to break pnpm install. https://github.com/unfold/heroku-buildpack-pnpm/blob/9a5caa934cceebc0f8c61b5c77fb41429630aeff/bin/compile#L225-L235Seeing this in logs
Looks like the script didn't wait until the install complete and start calling
pnpm
.