graphql-js: Error: Ensure that there are not multiple versions of GraphQL installed in your node_modules directory

I have two node modules A => B, where B creates a GraphQLSchema object that is imported by A, which is then used to instantiate graphqlExpress.

I get this error: Ensure that there are not multiple versions of GraphQL installed in your node_modules directory

And see that I have 2 different instances of the GraphQLSchema class type at runtime – so validate.js invariant(schema instanceof GraphQLSchema) fails because the imported schema is an instance of A’s GraphQLSchema not B’s GraphQLSchema.

However, all npm dependencies are of the same version (in both A and B modules).

> npm --version
3.10.7

> babel-node --version
6.16.0

> find node_modules -name graphql
node_modules/graphql
node_modules/graphql-subscriptions/node_modules/graphql

> grep version node_modules/graphql/package.json 
0.7.2

> grep version node_modules/graphql-subscriptions/node_modules/graphql/package.json
0.7.2

I assume this is a common pattern, but I can’t find an example.

BTW, I’m using npm-link to create the A => B dependency.

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 1
Comments: 27 (10 by maintainers)

Most upvoted comments

I have the following:

❯ find node_modules -name graphql
node_modules/graphql
❯ yarn list graphql
yarn list v1.22.5
warning Filtering by arguments is deprecated. Please use the pattern option instead.
└─ graphql@15.4.0
✨  Done in 1.65s.

So there’s definitely only one version, and yet:

Error: Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm.

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.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.

I’m in a typescript monorepo, so there’s no bundler or minifier, just the TS compiler. I have no idea what to do to isolate the issue.

+18

thekevinbrown on Jan 6, 2021

I have also faced this error, for example, my express-graphql uses graphql@11.x.x but I had installed graphql@8.x.x due to graphql-sequelize-crud uses a old version of graphql. I checked this out by this command

$ find node_modules -name graphql
node_modules/express-graphql/node_modules/graphql
node_modules/graphql

So I just run rm -rf node_modules/express-graphql/node_modules/graphql here and everything solved. Note that basically you need to only have 1 line result for find node_modules -name graphql

michaellee8 on Sep 6, 2017

All libraries should install graphql-js as a peer dependency so that a separate version is not installed. If this is not the case for some library, it should be reported as a bug to the library developers.

Otherwise, resolutions can be used with some package managers to force dependencies to use a single version.

Explorations have begun to support multiple packages for cjs/esm support, but you normally should not run into problems. graphql-tools in particular, as far as I am aware, correctly installs this library as a peer.

yaacovCR on Jul 20, 2022

One cause of this, other than having duplicate modules, is having graphql imported two different ways - e.g. having it imported as CommonJS in one location and having it imported as ESM in another location. This results in two independent sets of objects in memory and is one potential cause of this error. If you’re using a bundler you should be able to have it show you what it’s importing - if it’s importing both of these files then this is your issue:

benjie on Sep 24, 2021

I’m facing this problem today using yarn. I believe the source of this is that graphql-js is still using alpha versions (0.x…) and therefore the normal semver ranges don’t apply. So #1005 needs to be fixed.

jdachtera on Feb 15, 2018

A note for those still encountering this issue, yarn is pretty good at doing this version resolution, including support for a flag which enforces guarantees for a single version of every dependency if you want that. I believe npm5 also has some support for this kind of guarantee

leebyron on Aug 17, 2017

Got this issue as well.

Using node 7.9

$ find node_modules -name graphql

node_modules/@types/graphql
node_modules/graphql

should i just delete the @types/graphql directory?

I don’t think this should affect it but…

casoetan on Apr 14, 2017