Cannot use GraphQLObjectType "Query" from another module or realm

Bug report

I’m trying to implement this middleware in my express based graphql server. However on doing so I receive an error which is only there when applying this middleware.

Received error

Error: Cannot use GraphQLObjectType "Query" 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.

Code

import path from "path";
import { ApolloServer, makeExecutableSchema } from "apollo-server-express";
import { importSchema } from "graphql-import";
import { applyMiddleware } from "graphql-middleware";

import { shield, allow } from "graphql-shield";

import Mutation from "./resolvers/Mutation";
import Query from "./resolvers/Query";

const schema = makeExecutableSchema({
	typeDefs: importSchema(path.resolve("../src/schema.graphql")),
	resolvers: {
		Mutation,
		Query
	}
});

// No errors when you remove shield from the applyMiddleware call 
const adjustedSchema = applyMiddleware(schema, shield({}, { fallbackRule: allow }));

export default new ApolloServer({
	schema: adjustedSchema, // No errors when you pass schema: schema
	resolverValidationOptions: {
		requireResolversForResolveType: false
	},
	context: ctx => ctx
});

Versions used (all latest at this point in time)

"apollo-server-express": "^2.6.9",
"express": "^4.17.1",
"express-graphql": "^0.8.0",
"graphql": "^14.4.2",
"graphql-import": "^0.7.1",
"graphql-middleware": "^4.0.0",
"graphql-shield": "^6.0.4",
"prisma-binding": "^2.3.15"

How did I try to debug already

• Remove node_modules folder and run npm install
• Search the package-lock.json file for other versions specified for graphql, not the case

[maticzav]

@nealoke thank you so much for sharing all the progress, the solution, everything. Thanks!

I am genuinely glad you resolved it! 🙂

[nealoke]

I found the issue, and like I thought has nothing to do with this package. It basically was an issue with our setup which uses hoisting to pull all the dependencies to the root.

Inside the webpack.config.js I was using webpack-node-externals but only for the modules in the package (eg. packages/api/node_modules). So because most of the packages are pulled to the root it did not exclude these when building the server.js with webpack.

Before

{
    target: "node",
    externals: [
        nodeExternals({
            whitelist: "webpack/hot/poll?1000"
        })
    ]
    // ... Other config for webpack
}

After

{
    target: "node",
    externals: [
        nodeExternals({
            whitelist: "webpack/hot/poll?1000",
            modulesDir: path.resolve(__dirname, "../../node_modules")
        })
    ]
    // ... Other config for webpack
}