Skip to content

vue ui: Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm. #6191

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

Closed
CaiPeng1989 opened this issue Jan 7, 2021 · 0 comments · Fixed by #6192
Closed
Labels

Comments

@CaiPeng1989
Copy link

Version

5.0.0-alpha.2

Environment info

System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Binaries:
    Node: 15.5.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 2.4.0 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.3.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.423.0), Chromium (87.0.664.66), ChromiumDev (89.0.752.1)

Steps to reproduce

yarn global add @vue/cli@next
vue ui

What is expected?

normal operation.

What is actually happening?

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.

@haoqunjiang haoqunjiang added the bug label Jan 7, 2021
haoqunjiang added a commit to haoqunjiang/vue-cli that referenced this issue Jan 7, 2021
It causes peer dependency warnings because of several ill-maintained
apollo packages, but let's just ignore them.
Fixes vuejs#6191
haoqunjiang added a commit that referenced this issue Jan 11, 2021
It causes peer dependency warnings because of several ill-maintained
apollo packages, but let's just ignore them.
Fixes #6191
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants