Skip to content

pnpm peers check fails on semver range with dash at the end #12149

Description

@NiGhTTraX

Verify latest release

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

pnpm version

11.5.1

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

❯ pnpm -v
11.5.1

❯ pnpm add react-native-reanimated @gorhom/bottom-sheet

❯ pnpm peers check
Issues with peer dependencies found

✕ unmet peer react-native-reanimated
  Installed: 4.4.0
  Wanted:
    ">=3.16.0 || >=4.0.0-":
      @gorhom/bottom-sheet@5.2.14

Describe the Bug

@gorhom/bottom-sheet defines a >= 4.0.0- semver range with a dash at the end to cover -beta releases. See gorhom/react-native-bottom-sheet#2223 (comment) for more details.

pnpm peers check doesn't seem to like this range, printing a warning that the installed 4.4.0 version doesn't match that range. pnpm add or a cold pnpm install don't print any warnings.

Expected Behavior

No warnings on pnpm peers check.

Which Node.js version are you using?

24.13.1

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