Skip to content

pnpm up fails after opt-in paquet #11797

@Th3Trig3rFac3

Description

@Th3Trig3rFac3

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

v11.2.1

Which area(s) of pnpm are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

  1. pnpm self-update 11.2.1
  2. pnpm add @pnpm/pacquet --config
  3. pnpm up
  4. get error

Describe the Bug

pnpm up                          
[WARN] 1 deprecated subdependencies found: node-domexception@1.0.0
▶ Using pacquet for this install
  pacquet is pnpm's Rust install engine (preview); declared in configDependencies.
Progress: resolved 516, reused 0, downloaded 0, added 0
Error: pacquet_package_manager::outdated_lockfile
  × installing dependencies
  ╰─▶ Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json.
      
        Failure reason:
        specifiers in the lockfile don't match specifiers in package.json:
      * 1 dependency is mismatched:
        - @types/react (lockfile: ^19.2.15, manifest: ^19.2.14)
[ERR_PNPM_PACQUET_INSTALL_FAILED] pacquet exited with code 1e-only` so that pnpm-lock.yaml reflects the current package.json, then re-run `pacquet install --frozen-lockfile`.
Progress: resolved 516, reused 0, downloaded 0, added 0

It appears to have a version mismatch which was not present before opting in for paquet,

Expected Behavior

Successful update.

Which Node.js version are you using?

26.1.0

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions