Skip to content

packageManager/devEngines.packageManager conflict warning still showing for equivalent versions using hashes #12028

Description

@kleinfreund

Verify latest release

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

pnpm version

No response

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

CLI

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

No response

Reproduction steps

  1. Have a package.json with

    "devEngines": {
      "packageManager": {
        "name": "pnpm",
        "version": "11.4.0+sha512.f0febc7e37552ab485494a914241b338e0b3580b93d54ce31f00933015880863129038a1b4ae4e414a0ee63ac35bf21197e990172c4a68256450b5636310968f"
      }
    },
    "packageManager": "pnpm@11.4.0+sha512.f0febc7e37552ab485494a914241b338e0b3580b93d54ce31f00933015880863129038a1b4ae4e414a0ee63ac35bf21197e990172c4a68256450b5636310968f"

    i.e. both pnpm versions are virtually identical and the hash form is used (without the hash form, the issue doesn't happen)

  2. Run pnpm --version

Describe the Bug

The warning Cannot use both "packageManager" and "devEngines.packageManager" in package.json. "packageManager" will be ignored is logged.

Expected Behavior

The warning Cannot use both "packageManager" and "devEngines.packageManager" in package.json. "packageManager" will be ignored is not logged (as per #11307).

Which Node.js version are you using?

24.16.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

    Fields

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions