question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Old versions of graphql required - Can't use with new version of Prisma

See original GitHub issue

Since updating Prisma, I get the same error as shown here - https://www.prisma.io/forum/t/duplicate-graphql-error-out-of-nowhere/5849

Ensure that there is only one instance of “graphql” in the node_modules ▸ directory. If different versions of “graphql” are the dependencies of ▸ other ▸ relied on modules, use “resolutions” to ensure only one version is ▸ installed.

It appears that graphql-yoga is importing older versions of libraries, which required out of date versions of graphql. Can these be updated? See the list below. For instance, graphql-subscriptions is now at 1.1, but this library requires 0.60.

warning "graphql-yoga > graphql-subscriptions@0.5.8" has incorrect peer dependency "graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0".
warning "graphql-yoga > apollo-server-express > apollo-server-core@1.4.0" has incorrect peer dependency "graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0".
warning "graphql-yoga > apollo-server-express > apollo-server-core > apollo-cache-control@0.1.1" has incorrect peer dependency "graphql@0.10.x - 0.13.x".
warning "graphql-yoga > apollo-server-express > apollo-server-core > apollo-tracing@0.1.4" has incorrect peer dependency "graphql@0.10.x - 0.13.x".
warning "graphql-yoga > apollo-server-express > apollo-server-core > graphql-extensions@0.0.10" has incorrect peer dependency "graphql@0.10.x - 0.13.x".

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:19
  • Comments:12

github_iconTop GitHub Comments

6reactions
stale[bot]commented, Sep 3, 2019

Due to inactivity of this issue we have marked it stale. It will be closed if no further activity occurs.

4reactions
pilattecommented, Sep 3, 2019

@heymartinadams If GitHub wasn’t littered with stale bots, I would not write stupid comments like the one I’m writing right now.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Old versions of graphql required - Can't use with new ... - GitHub
It appears that graphql-yoga is importing older versions of libraries, which required out of date versions of graphql. Can these be updated?
Read more >
Duplicate GraphQL Error Out of Nowhere - Questions - Prisma 1
If different versions of “graphql” are the dependencies of ▸ other ▸ relied on modules, use “resolutions” to ensure only one version is...
Read more >
Upgrading from Prisma 1 with prisma-binding to SDL-first
Overview. This upgrade guide describes how to migrate a Node.js project that's based on Prisma 1 and uses prisma-binding to implement a GraphQL...
Read more >
Error message reference - Prisma
Prisma Client throws a PrismaClientUnknownRequestError exception if the query engine returns an error related to a request that does not have an error...
Read more >
How to upgrade from Prisma 1 to Prisma version 2.x and later
Once you're done with that guide, you can choose one of the following four guides to upgrade your application layer: Old to new...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found