Skip to content

package.json keeps my pnpm version artificially old #587

Closed
@hyperknot

Description

@hyperknot

I opened this issue in pnpm but it seems it's more related to corepack.

https://github.com/orgs/pnpm/discussions/8911#discussioncomment-11674247

Copying it here:


  1. I go to any repo, with package.json
  2. I run pnpm i
  3. It adds this "packageManager": "[email protected]+sha512...." line
  4. From now on: 1. it keeps annoying me with the "Please update pnpm with corepack" notice AND 2. it doesn't get updated.

By "doesn't get updated" I mean that even though I've updated my pnpm to the latest version, when I go inside that directory, it reports it as 9.10, not as 9.15.

Even though I'm running on the very same binary file!

Outside the project repo:

/Users/user/.nvm/versions/node/v20.17.0/bin/pnpm --version
9.15.1

Inside the project repo:

/Users/user/.nvm/versions/node/v20.17.0/bin/pnpm --version
9.10.0

This is extremely buggy / confusing like this. How can the same binary file have multiple versions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions