Closed
Description
The problem is that graphqljs doesn't publish "real" ESM, (they're using the "module" field). So a Node ESM project will resolve to the CJS version of the files when importing exports via "graphql", eg import { GraphQLObjectType } from "graphql". This package however deep imports ESM from graphqljs. Instead it should not deep import so shared dependencies resolve correctly.
The error is:
Error: Cannot use GraphQLObjectType "__Type" 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.
Metadata
Metadata
Assignees
Labels
No labels