GraphiQL produces error: Cannot use e "__Schema" from another module or realm.

[slikts]

I'm submitting a ...

• bug report

PostGraphQL version: 3.5.5

Steps to reproduce:

I run postgraphql -c postgres://user@localhost/db

I've tried with postgraphql installed globally or locally; possibly related to minifaction graphql/graphql-js#1182

Current behavior:

Uncaught Error: Cannot use e "__Schema" 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.

    at n (instanceOf.js:17)```

[benjie]

Ugh; it worked locally. I'll get another release shipped.

[benjie]

3.5.6 is out which fixes this; I've specifically installed graphql v0.11 locally before building/publishing.

[benjie]

And postgraphile@4.0.0-alpha2.30

[baldwinchang]

Hi @benjie, what would be the ETA on the docker image build also reflecting the update?

Thanks!

---

Update: The error still seems to be showing for me on /graphiql on fix-send and latest tags on Docker Hub.

[benjie]

The docker images will need manual fixing to pin graphql to v0.11 as v0.12 breaks minification. I would pin it in the package.json, but doing so would be a breaking change. Paging @angelosarto

[angelosarto]

Will take a look tonight should be straightforward.

…

On Wed, Jan 31, 2018 at 4:33 PM Benjie Gillam ***@***.***> wrote: The docker images will need manual fixing to pin graphql to v0.11 as v0.12 breaks minification. I would pin it in the package.json, but doing so would be a breaking change. Paging @angelosarto <https://github.com/angelosarto> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#677 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABefi6dXjOeCLf7jUXcZ3WO3PqjPMimvks5tQOpJgaJpZM4Ryo_h> .

[benjie]

Thanks @angelosarto! 🙏

[angelosarto]

If the above PR is merged - docker should automatically rebuild and it will temporary pin the version before the package is built. I tried it locally and it seems fine.

[benjie]

Merged 👍

[idkjs]

Getting the same, above noted error, with version "postgraphile@4.0.0-alpha2.33"

Im running through the tutorial and trying to run the following command postgraphile -c postgres://forum_example_postgraphile:xyz@localhost:5432/mydb from the POSTGRES ROLES Section.

Im getting this error in the console:

postgraphile -c postgres://forum_example_postgraphile:xyz@localhost:5432/forum

PostGraphQL server listening on port 5000 🚀

  ‣ Connected to Postgres instance postgres://localhost:5432/forum
  ‣ Introspected Postgres schema(s) public
  ‣ GraphQL endpoint served at http://localhost:5000/graphql
  ‣ GraphiQL endpoint served at http://localhost:5000/graphiql

* * *

Failed to add function 'public.crypt'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
Failed to add function 'public.dearmor'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
Failed to add function 'public.decrypt'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
Failed to add function 'public.decrypt_iv'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
Failed to add function 'public.encrypt'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
Failed to add function 'public.encrypt_iv'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
Failed to add function 'public.pgp_key_id'; run with 'DEBUG="graphile-build-pg:warn"' to view the error
An error occurred, it might be okay but it doesn't look like the error we were expecting... run with envvar 'DEBUG="graphile-build:warn"' to view the error
    Error: Cannot use GraphQLSchema "[object Object]" 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.
    at instanceOf (/Users/prisc_000/.config/yarn/global/node_modules/postgraphile/node_modules/graphql/jsutils/instanceOf.js:17:13)
    at isSchema (/Users/prisc_000/.config/yarn/global/node_modules/postgraphile/node_modules/graphql/type/schema.js:48:35)
    at validateSchema (/Users/prisc_000/.config/yarn/global/node_modules/postgraphile/node_modules/graphql/type/validate.js:51:25)
    at assertValidSchema (/Users/prisc_000/.config/yarn/global/node_modules/postgraphile/node_modules/graphql/type/validate.js:76:16)
    at Object.validate (/Users/prisc_000/.config/yarn/global/node_modules/postgraphile/node_modules/graphql/validation/validate.js:61:35)
    at Object.<anonymous> (/Users/prisc_000/.config/yarn/global/node_modules/postgraphile/build/postgraphql/http/createPostGraphQLHttpRequestHandler.js:333:50)
    at step (/Users/prisc_000/.config/yarn/global/node_modules/tslib/tslib.js:133:27)
    at Object.next (/Users/prisc_000/.config/yarn/global/node_modules/tslib/tslib.js:114:57)
    at fulfilled (/Users/prisc_000/.config/yarn/global/node_modules/tslib/tslib.js:104:62)
    at <anonymous>
1 error(s) in 51.61ms :: query IntrospectionQuery { __schema { queryType { name } mutationType { name } subscriptionType { name } types { ...FullType } directives { name description locations args { ...InputValue } } } } fragment FullType on __Type { kind name description fields(includeDeprecated: true) { name description args { ...InputValue } type { ...TypeRef } isDeprecated deprecationReason } inputFields { ...InputValue } interfaces { ...TypeRef } enumValues(includeDeprecated: true) { name description isDeprecated deprecationReason } possibleTypes { ...TypeRef } } fragment InputValue on __InputValue { name description type { ...TypeRef } defaultValue } fragment TypeRef on __Type { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name } } } } } } } }
^C

Enviroment:
ProductName: Mac OS X
ProductVersion: 10.13.3
BuildVersion: 17D102
yarn version: 1.5.1
node version: v9.5.0

[benjie]

Follow the yarn resolution instructions in the error message to ensure there’s only one version of graphql installed. Probably 0.11.x

[mike-022]

Yarn resolution worked for me:

"dependencies": {
"babel-cli": "^6.26.0",
"config": "^1.26.2",
"cookie-parser": "^1.4.3",
"dotenv": "^4.0.0",
"express": "^4.13.3",
"graphql": "0.13.2",
"node-fetch": "^1.7.3",
"postgraphile": "^4.0.0-alpha2.20"
},
"resolutions": {
"postgraphile/graphql": "0.13.2"
},

[nmgds]

any solution for npm? have exactly the same as @MichaelG02

[benjie]

For yarn you’d do this: https://stackoverflow.com/questions/51990179/run-postgraphile-with-npm/51990635#51990635

Here’s some comments about it on the GraphQL repo, perhaps there might be something there that might point you somewhere useful for npm:

graphql/graphql-js#594 (comment)

I don’t use npm, but if you get a solution please report back 👍

[benjie]

“npm dedupe” might work. Use 0.12.x if you can.

[nmgds]

@benjie thank you for pointing the right direction. I did try npm dedupe before, but without success. Fortunately lowering down graphql to 0.12.3 helped!

[omar-dulaimi]

I get this error despite running postgraphile with npx. Any tips?

[benjie]

Do it in a clean folder whose ancestors have no node_modules folders

[omar-dulaimi]

@benjie running it from root fixed the issue. Thank you!