Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Not respecting pnpm version specified in packageManager field of package.json #899

Open
sapphi-red opened this issue Jan 20, 2023 · 1 comment
Labels
type: bug code to address defects in shipped code

Comments

@sapphi-red
Copy link

Is your build failing?
No

Describe the bug
It's documented that pnpm version of packageManager is used.

To specify a pnpm version, you can edit your package.json file:
https://docs.netlify.com/configure-builds/manage-dependencies/#pnpm

But the default version (7.13.4) is used even if packageManager field exists.

To Reproduce

Steps to reproduce the behavior:

  1. Fork the repository at https://github.com/sapphi-red-repros/netlify-pnpm-cannot-iterate-over-repro
  2. Checkout commit 204df13623a9a831a0a663844fa02fb49b531dd2
  3. Create a Netlify site and link it to the forked repository
  4. See that the Netlify build uses [email protected] (log)

Configuration

[build.environment]
  NODE_VERSION = "16"
[build]
  publish = "packages/foo/.vitepress/dist"
  command = "pnpm build-foo"

Expected behavior
[email protected] is used.

Build Output
N/A

Additional context
I guess this is happening because of this error when running mv.
https://app.netlify.com/sites/dashing-marzipan-db6e0f/deploys/63ca21d3e60cb2209d3758ad#L23

@sapphi-red sapphi-red added the type: bug code to address defects in shipped code label Jan 20, 2023
@sapphi-red
Copy link
Author

Ah, no, I was wrong. [email protected] is actually used. But the activation for [email protected] is running even if it's not needed, I guess.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug code to address defects in shipped code
Projects
None yet
Development

No branches or pull requests

1 participant