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

Incorrect Peer Dependency warning #2531

Open
awx-erik-yu opened this issue Dec 24, 2021 · 1 comment · May be fixed by #2532
Open

Incorrect Peer Dependency warning #2531

awx-erik-yu opened this issue Dec 24, 2021 · 1 comment · May be fixed by #2532

Comments

@awx-erik-yu
Copy link

Intended outcome:

installing without warning output.

Actual outcome:

warning "apollo > apollo-language-server > @apollographql/[email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning "apollo > apollo-language-server > @apollographql/graphql-language-service-interface > @apollographql/[email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning "apollo > apollo-language-server > @apollographql/graphql-language-service-interface > @apollographql/[email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning "apollo > apollo-language-server > @apollographql/graphql-language-service-interface > @apollographql/[email protected]" has incorrect peer dependency "graphql@^0.12.0 || ^0.13.0 || ^14.0.0".

How to reproduce the issue:

  • npm init
  • yarn add apollo

Versions

latest

@tjmoses
Copy link

tjmoses commented Jan 12, 2022

It seems the graphql-language-service-interface 2.0.2 is the only package still reliant an older dependency of graphql:
image
It appears version 2.10.2, that you added, uses ^15.5.0 || ^16.0.0, which seems to be the perfect fix. Were you able to get the PR issues resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants