Update to graphql 0.13.0 crashes subscriptions #162

MitkoTschimev · 2018-02-11T17:26:18Z

Update:

Add the following to your package.json and run yarn install. This should fix the problem:

  "resolutions": {
    "graphql": "0.13.1"
  }

After updating to graphql-yoga to 1.2.5 subscriptions are not working anymore because of duplicated graphql version. And a lot of warnings are throwing on yarn installation -> i think that the deps are not compatible with 0.13.0

warning "graphql-yoga > [email protected]" has incorrect peer dependency "[email protected] - 0.12".
warning "graphql-yoga > [email protected]" has incorrect peer dependency "graphql@^0.10.5 || ^0.11.3 || ^0.12.0".
warning "graphql-yoga > [email protected]" has incorrect peer dependency "graphql@^0.11.0 || ^0.12.0".
warning "graphql-yoga > [email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0".
warning "graphql-yoga > apollo-server-express > [email protected]" has incorrect peer dependency "graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0".
warning "graphql-yoga > apollo-server-express > apollo-server-core > [email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0".
warning "graphql-yoga > apollo-server-express > apollo-server-core > [email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0".
warning "graphql-yoga > apollo-server-express > apollo-server-core > [email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0".

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.

The text was updated successfully, but these errors were encountered:

MitkoTschimev · 2018-02-12T09:18:20Z

After a rollback to a previous version it works again
my entries in the working version of package.json

"dependencies": {
    "aws-lambda": "^0.1.2",
    "aws-sdk": "2.192.0",
    "bcryptjs": "2.4.3",
    "graphql-yoga": "1.2.4",
    "jsonwebtoken": "8.1.1",
    "prisma-binding": "1.5.7"
  },
  "devDependencies": {
    "@types/bcryptjs": "2.4.1",
    "dotenv-cli": "1.4.0",
    "graphql-cli": "2.13.2",
    "nodemon": "1.14.12",
    "npm-run-all": "4.1.2",
    "prisma": "1.1.3",
    "rimraf": "2.6.2",
    "ts-node": "4.1.0",
    "typescript": "2.6.2"
  }

ragzor · 2018-02-12T18:54:02Z

Same Issue.

"dependencies": {
"bcryptjs": "2.4.3",
"graphql-yoga": "^1.2.5",
"jsonwebtoken": "8.1.0",
"prisma-binding": "^1.5.9"
},
"devDependencies": {
"dotenv": "4.0.0",
"nodemon": "1.14.10"
}

oxy88 · 2018-02-13T01:49:44Z

Same. I had to add resolutions [email protected] in package.json and subscriptions don't work correctly

schickling · 2018-02-13T09:25:07Z

We're looking into this! 🕵️

zifahm · 2018-02-14T04:03:45Z

getting a similar error here https://imgur.com/a/nMqHG

schickling · 2018-02-14T14:13:54Z

Can you all please try to update prisma-binding to the latest version? This should fix the issue.

gihrig · 2018-02-14T21:02:46Z

@schickling Works for me! 💯

Thanks! 🎉 ✨

lewisblackwood · 2018-02-20T19:14:40Z

👋I'm seeing the same error using the typescript-advanced Prisma boilerplate, with latest versions installed.

My dependencies look like this:

"dependencies": {
  "bcryptjs": "2.4.3",
  "graphql-yoga": "1.3.3",
  "jsonwebtoken": "8.1.1",
  "prisma-binding": "1.5.12"
},
"devDependencies": {
  "@types/bcryptjs": "2.4.1",
  "dotenv-cli": "1.4.0",
  "graphql-cli": "2.14.2",
  "nodemon": "1.15.1",
  "npm-run-all": "4.1.2",
  "prisma": "1.2.4",
  "rimraf": "2.6.2",
  "ts-node": "4.1.0",
  "typescript": "2.7.2"
}

niclone · 2018-02-21T15:37:04Z

Hi,

I had the same problem, finally solved by removing yarn (sudo npm remove -g yarn) before prisma init, and then install it again (sudo npm install -g yarn) before "yarn dev"...

schickling · 2018-02-21T15:42:01Z

For everyone still having problems with this, please try the following things if the error still appears:

yarn upgrade-interactive --latest and make sure you're running the newest version of the following packages (if used)
- prisma-binding
- graphql-yoga
- prisma
- graphql-cli
rm -rf node_modules
yarn install

schickling · 2018-02-21T15:42:47Z

@niclone glad it works for you now, reinstalling yarn should actually not be necessary.

Hopefully this all will go a lot smoother for future graphql releases.

niclone · 2018-02-21T15:49:45Z

@schickling : resintall yarn is not the solution, the solution is to have it UNINSTALLED during prisma init.

iamclaytonray · 2018-02-21T18:47:38Z

I wish I could find the relevant issue but I haven't been able to find it...

From what I remember, the issue is that Yarn tries to install graphql multiple times, at different versions. You'll find that rm -rf node_modules && npm i works perfectly, regardless of what graphql version you have. I'll try to find it again, again

Also, from what I remember, it also has to do with setting graphql as a dep instead of peer dep, which causes multiple versions of graphql being installed and breaking

tobkle · 2018-02-21T19:04:30Z

This doesn't work:

yarn upgrade-interactive --latest
rm -rf node_modules
yarn install
yarn dev

I'm still getting the duplicate graphql error.

But this works:

yarn upgrade-interactive --latest
rm -rf node_modules
npm install
yarn dev

or you add to package.json:

"resolutions": {
    "graphql": "^0.13.0"
}

gihrig · 2018-02-21T19:32:43Z

But this works:

yarn upgrade-interactive --latest
rm -rf node_modules
npm install
yarn dev

Sounds like you may need to clear yarn's cache

yarn cache clean

schickling · 2018-02-21T19:38:15Z

Thanks for pointing this out @tobkle. Add the following to your package.json and run yarn install. This should fix the problem:

  "resolutions": {
    "graphql": "0.13.1"
  }

the-simian · 2018-02-22T06:51:58Z

@schickling I am still getting this very issue, even after adding the resolutions property to the package.json.

The only thing that worked for me was downgrading to 1.2.4, anything higher would always cause the issue.

I also had to use npm -i instead of yarn as well.

schickling · 2018-02-25T16:53:34Z

By now all packages have been updated, so with the newest package versions this should now work even without the resolutions addition.

marktani · 2018-02-26T10:09:22Z

For anyone still running into this, upgrading yarn from 0.27.5 to 1.3.2 fixed it for me.

johnbendi · 2018-04-26T04:22:31Z

This issue is still happening for me with yarn version 1.6.0 even with the resolutions fix.

elie222 · 2018-05-07T19:53:28Z

I'm also getting this issue here:
apollographql/subscriptions-transport-ws#411

jhalborg · 2018-05-29T10:40:48Z

Getting this issue after using typescript-advanced boilerplate and following part 1 of the guide for deploying with now. I then realized that I needed to check out part two as well. Deploying with now --dotenv .env worked

Urigo · 2022-03-29T14:10:21Z

Hey, @Urigo from The Guild here!

You might know us from projects such as graphql-code-generator, envelop or graphql-tools.

For a long time we thought that the Javascript ecosystem is still missing a lightweight cross-platform, but still highly customizable GraphQL Server.

In the past the awesome Prisma team took on that great challenge and now we are happy to announce that we are continuing them and just released GraphQL Yoga 2.0 - Build fast, extensible, and batteries-included (Subscriptions, Serverless, File uploads support) GraphQL APIs in Node.js 🚀

We have been working a long time on version 2.0 and have been using it in our clients projects for a few months now and shared a couple of alpha cycles here.
Thank you all for your feedback and suggestions, you made this release possible!

Please try Yoga out again, give us feedback and help us spread the word on the new release!

This was referenced Feb 12, 2018

Remove graphql dependency este/este#1465

Closed

unfix prima depencies este/este#1466

Closed

marktani mentioned this issue Feb 13, 2018

5 hours prisma/prisma1#1881

Closed

schickling closed this as completed Feb 14, 2018

marktani mentioned this issue Feb 21, 2018

Error: Duplicate "graphql" modules graphql-boilerplates/node-graphql-server#211

Closed

danielsbird mentioned this issue Mar 31, 2018

Unexpected token I in JSON at position 0 howtographql/react-apollo#32

Closed

elie222 mentioned this issue May 7, 2018

Cannot use GraphQLSchema [object Object] from another module or realm. apollographql/subscriptions-transport-ws#411

Closed

donLucho mentioned this issue Sep 24, 2018

An error occured vue-apollo.js:55:4 vuejs/vue-cli#2577

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update to graphql 0.13.0 crashes subscriptions #162

Update to graphql 0.13.0 crashes subscriptions #162

MitkoTschimev commented Feb 11, 2018 •

edited by schickling

Loading

MitkoTschimev commented Feb 12, 2018

ragzor commented Feb 12, 2018

oxy88 commented Feb 13, 2018

schickling commented Feb 13, 2018

zifahm commented Feb 14, 2018

schickling commented Feb 14, 2018

gihrig commented Feb 14, 2018

lewisblackwood commented Feb 20, 2018

niclone commented Feb 21, 2018

schickling commented Feb 21, 2018

schickling commented Feb 21, 2018

niclone commented Feb 21, 2018

iamclaytonray commented Feb 21, 2018 •

edited

Loading

tobkle commented Feb 21, 2018 •

edited by schickling

Loading

gihrig commented Feb 21, 2018

schickling commented Feb 21, 2018

the-simian commented Feb 22, 2018 •

edited

Loading

schickling commented Feb 25, 2018

marktani commented Feb 26, 2018

johnbendi commented Apr 26, 2018

elie222 commented May 7, 2018

jhalborg commented May 29, 2018

Urigo commented Mar 29, 2022

Update to graphql 0.13.0 crashes subscriptions #162

Update to graphql 0.13.0 crashes subscriptions #162

Comments

MitkoTschimev commented Feb 11, 2018 • edited by schickling Loading

MitkoTschimev commented Feb 12, 2018

ragzor commented Feb 12, 2018

oxy88 commented Feb 13, 2018

schickling commented Feb 13, 2018

zifahm commented Feb 14, 2018

schickling commented Feb 14, 2018

gihrig commented Feb 14, 2018

lewisblackwood commented Feb 20, 2018

niclone commented Feb 21, 2018

schickling commented Feb 21, 2018

schickling commented Feb 21, 2018

niclone commented Feb 21, 2018

iamclaytonray commented Feb 21, 2018 • edited Loading

tobkle commented Feb 21, 2018 • edited by schickling Loading

gihrig commented Feb 21, 2018

schickling commented Feb 21, 2018

the-simian commented Feb 22, 2018 • edited Loading

schickling commented Feb 25, 2018

marktani commented Feb 26, 2018

johnbendi commented Apr 26, 2018

elie222 commented May 7, 2018

jhalborg commented May 29, 2018

Urigo commented Mar 29, 2022

MitkoTschimev commented Feb 11, 2018 •

edited by schickling

Loading

iamclaytonray commented Feb 21, 2018 •

edited

Loading

tobkle commented Feb 21, 2018 •

edited by schickling

Loading

the-simian commented Feb 22, 2018 •

edited

Loading