-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Error: Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm. #532
Comments
Oh and if someone can help point out what the problem is then I'll surely submit a patch to the build system to detect this condition or a superclass of this condition. |
I think the root cause of this kind of error is when there are multiple Can you run |
|
Those errors don't look very promising. This might be related to you using Node v15. Could you try with v12 or v14 and see if things work better? |
MacOS homebrew install.
I'm considering never doing dev work on anything other than a common Linux
distro 🙂
…On Tue., 27 Oct. 2020, 17:19 Michael Bromley, ***@***.***> wrote:
Those errors don't look very promising. This might be related to you using
Node v15. Could you try with v12 or v14 and see if things work better?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#532 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARIHHIERLLQLS6SZSBR4RITSM3XJLANCNFSM4TA6D5RQ>
.
|
I had the same problem, changing Node version to v12 worked for me, I didn't try with v14. Thanks! |
Hello guys, I tried latest v14 on latest MacOS and it worked. After updating to latest npm (v7.5.3) got the above mentioned problem. Thanks! |
I think this is related to the way npm v7 handles peerDependencies. For now, avoid npm v7, i.e use v6 or yarn. |
I got the same problem on Node |
Relates to #532 Changes to e2e tests relate to the new handling of bad user input described here: https://github.com/apollographql/apollo-server/ blob/9267a79b974e397e87ad9ee408b65c46751e4565/CHANGELOG.md#v2230
This is currently blocked because of an upstream regression in the nestjs/graphql package (nestjs/graphql#1468) which prevents me from updating to the latest version. As a result, installing with npm v7 will result in multiple conflicting versions of the As soon as the Nestjs/graphql issue is resolved we can update that package and this issue should also resolve at that point. |
Added a work-around which allows the update of the nestjs/graphql package. This solves the npm v7 issue! |
Describe the bug
Attempting to launch the web app results in: "Error: Cannot use GraphQLSchema "[object GraphQLSchema]" from another module or realm."
To Reproduce
npx @vendure/create my-app
Expected behavior
Starts the services.
Environment (please complete the following information):
Additional context
It's almost certainly a problem with my environment because no-one else is complaining and also it sounds like some dependency conflict of graphsql module versions. I am clearly not a Node.js person :-)
The text was updated successfully, but these errors were encountered: