We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Related problem #2439
When we compile our node server using babel, the node server works well
however, when we bundle the node server using webpack, it throws this error
Error: Schema must contain uniquely named types but contains multiple types named "ID"
I've tracked down as the collectReferencedTypes (
collectReferencedTypes
graphql-js/src/type/schema.ts
Line 193 in 69e1554
we use graphql-js and graphql-relay, we ensure we only have 1 version of them in our monorepo
we have many schemas in our monorepo (7 schemas)
We also tried to understand if GraphQLScalarType ID was being called twice, but it was only once
what is the best way to understand and debug this kind of bug?
graphql@16.5.0 graphql-relay@0.7.0
The text was updated successfully, but these errors were encountered:
node + babel consume .js files webpack consumes .mjs files
Sorry, something went wrong.
I had an import like this
import { GraphQLID } from 'graphql/type/scalars';
moving to
import { GraphQLID } from 'graphql';
solved the problem
No branches or pull requests
Reporting issues with GraphQL.js
Related problem #2439
When we compile our node server using babel, the node server works well
however, when we bundle the node server using webpack, it throws this error
I've tracked down as the
collectReferencedTypes
(graphql-js/src/type/schema.ts
Line 193 in 69e1554
we use graphql-js and graphql-relay, we ensure we only have 1 version of them in our monorepo
we have many schemas in our monorepo (7 schemas)
We also tried to understand if GraphQLScalarType ID was being called twice, but it was only once
what is the best way to understand and debug this kind of bug?
graphql@16.5.0
graphql-relay@0.7.0
The text was updated successfully, but these errors were encountered: