Skip to content
New issue

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

graphql-parse-resolve-info: Import is causing issues with bundler #869

Open
Maniload opened this issue Jan 12, 2025 · 0 comments
Open

graphql-parse-resolve-info: Import is causing issues with bundler #869

Maniload opened this issue Jan 12, 2025 · 0 comments

Comments

@Maniload
Copy link

Summary

Hello 👋 I'm using the graphql-parse-resolve-info package for a frontend project, which means it goes through a bundler (in my case that is Next.js). After upgrading my graphql version to 16.x I'm experiencing some weird errors that look like this:

Cannot use GraphQLScalarType "String" 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.

Of course I checked that I don't have duplicate graphql versions. In fact I could track this issue down to a line in this package:

import { getArgumentValues } from "graphql/execution/values";

It looks like the issue is that getArgumentValues is not imported directly from graphql but rather from a sub-directory. I assume that is because it is only exposed since this commit: graphql/graphql-js@6871bad, which landed in version 16.4.0.

When I change this line to import directly from graphql, the error from above is gone. To be fair this is probably also caused by my bundler and using this package with a bundler is probably a niche use-case anyways.

Additional context

Relevant package versions:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant