Dependency Issue with Graphql v15 vs v16
See original GitHub issueQuestion about GraphQL Shield
Hello! I’m trying to add graphql-shield to one of my projects, but I can not install it. It looks like that I can’t use it with graphql v16.x.x
With v15 i get it to work. Is this normal?
npm ERR! Found: graphql@16.3.0
npm ERR! node_modules/graphql
npm ERR! graphql@"^16.3.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer graphql@"^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0" from graphql-shield@7.5.0
npm ERR! node_modules/graphql-shield
npm ERR! graphql-shield@"^7.5.0" from the root project
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:21
- Comments:16 (1 by maintainers)
Top Results From Across the Web
GraphQL.js v16 support · Issue #1100 · MichalLytek/type ...
TypeGraphQL itself only depends on graphql-query-complexity and graphql-subscriptions , but there are also quite a few dev dependencies that I ...
Read more >Migrating to Apollo Server 4 - Apollo GraphQL Docs
Apollo Server has a peer dependency on graphql (the core JS GraphQL implementation). Apollo Server 4 supports graphql v16.6.0 and later. (Apollo Server...
Read more >Migrating from v4 to v5 - Gatsby
The internal graphql dependency was updated from v15 to v16. In most cases this change will be invisible to you and no action...
Read more >graphql - npm
This runs a query fetching the one field defined. The graphql function will first ensure the query is syntactically and semantically valid ...
Read more >GraphQL ERESOLVE unable to resolve dependency tree ...
The problem here is certainly with NPM and the packages you are trying to install rather than anything to do with Docker.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just use https://www.graphql-tools.com/docs/resolvers-composition 👍🏼
Probably shouldn’t close this one? Updating for graphQL 16 compatibility I guess would be the fix?