Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(bug) peerDependency on Cypress 4.x #232

Open
dwilches opened this issue Feb 24, 2023 · 4 comments
Open

(bug) peerDependency on Cypress 4.x #232

dwilches opened this issue Feb 24, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@dwilches
Copy link

Describe the bug
The package.json mentions the latest version of this plugin is only compatible with Cypress 4.x:

  "peerDependencies": {
    "cypress": "^4.5.0"
  },

Is this a mistake and that should be >4.5.0 or really this plugin is only compatible with a version of Cypress released on 2020?

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: my-project@1.0.0
npm ERR! Found: cypress@12.6.0
npm ERR! node_modules/cypress
npm ERR!   dev cypress@"^12.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer cypress@"^4.5.0" from cypress-plugin-snapshots@1.4.4
npm ERR! node_modules/cypress-plugin-snapshots
npm ERR!   cypress-plugin-snapshots@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
@dwilches dwilches added the bug Something isn't working label Feb 24, 2023
@ninaDeimos
Copy link

Is there any update on this? Or if this repository is no longe maintained, is there a successor of this package?

@ozkoidi
Copy link

ozkoidi commented Aug 9, 2023

I'm also waiting for this to be resolved. Every time I run npm install I get the warning about that dependency

image

@marabesi
Copy link

marabesi commented Sep 9, 2023

+1

@SimonLandeholm
Copy link

You can use npm i --legacy-peer-deps as a workaround meanwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants