Skip to content

Dependency resolution not deterministic #6154

Description

@unional

pnpm version:

7.28.0 with lockfile v6

Code to reproduce the issue:

I was work on this: #5585 (comment)

I delete the lockfile and node_modules folder and start again,
this time it resolves the dependency issue.

I then remove the overrides field and test how it works.

When I look at the lock file, I saw many changes.
I was expecting it just remove the overrides and maybe adjust (mess up) dependencies related to webpack.

But I found changes like these:

Actual behavior:

eslint-plugin-harmony:
  specifier: ^7.1.1
- version: 7.1.1(@typescript-eslint/eslint-plugin@5.54.0)(eslint-config-prettier@8.6.0)(eslint@8.35.0)(typescript@4.9.5)  
+ version: 7.1.1(@typescript-eslint/eslint-plugin@5.54.0)(eslint@8.35.0)(typescript@4.9.5)

'@storybook/addon-docs':
  specifier: ^7.0.0-beta.47
- version: 7.0.0-beta.56(@storybook/mdx1-csf@1.0.0-next.1)(react-dom@16.14.0)(react@16.14.0)
+ version: 7.0.0-beta.56(react-dom@16.14.0)(react@16.14.0)

... and many more

Since the actual version installed is the same (they are the latest),
the resolution really should stay the same.

Additional information:

  • node -v prints: v16.19.0
  • Windows, macOS, or Linux?: macOS

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions