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

Old versions of graphql required - Can't use with new version of Prisma #573

Closed
vjsingh opened this issue Jun 25, 2019 · 12 comments
Closed

Comments

@vjsingh
Copy link

vjsingh commented Jun 25, 2019

Since updating Prisma, I get the same error as shown here - https://www.prisma.io/forum/t/duplicate-graphql-error-out-of-nowhere/5849

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.

It appears that graphql-yoga is importing older versions of libraries, which required out of date versions of graphql. Can these be updated? See the list below. For instance, graphql-subscriptions is now at 1.1, but this library requires 0.60.

warning "graphql-yoga > [email protected]" has incorrect peer dependency "graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.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 || ^0.13.0".
warning "graphql-yoga > apollo-server-express > apollo-server-core > [email protected]" has incorrect peer dependency "[email protected] - 0.13.x".
warning "graphql-yoga > apollo-server-express > apollo-server-core > [email protected]" has incorrect peer dependency "[email protected] - 0.13.x".
warning "graphql-yoga > apollo-server-express > apollo-server-core > [email protected]" has incorrect peer dependency "[email protected] - 0.13.x".
@stale
Copy link

stale bot commented Sep 3, 2019

Due to inactivity of this issue we have marked it stale. It will be closed if no further activity occurs.

@stale stale bot added status/stale and removed status/stale labels Sep 3, 2019
@vjsingh
Copy link
Author

vjsingh commented Sep 3, 2019

I believe this is still relevant

@pilattebe
Copy link

@heymartinadams If GitHub wasn't littered with stale bots, I would not write stupid comments like the one I'm writing right now.

@bigman73
Copy link

graphql-yoga introduces many warnings:

npm WARN [email protected] requires a peer of [email protected] - 0.13.x but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of graphql@^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of [email protected] - 0.13.x but none is installed. You must install peer dependencies yourself.

Please fix the dependencies
Expected result: 0 npm warnings due to graphql-yoga

@heymartinadams
Copy link

I don’t think graphql-yoga will continue to be maintained. I switched to apollo-server or apollo-server-micro (for creating a GraphQL server using serverless function endpoints).

@bigman73
Copy link

Thanks.
Do you know the reason for that?

@ragzor
Copy link

ragzor commented Apr 16, 2020

I don’t think graphql-yoga will continue to be maintained. I switched to apollo-server or apollo-server-micro (for creating a GraphQL server using serverless function endpoints).

same! but unfortunately apollo server + prisma + nexus don't play well together for us, something breaks literally everyday :/

@heymartinadams
Copy link

heymartinadams commented Apr 16, 2020

Not sure, @bigman73. Maybe b/c they’re focused on their core offerings?

@ragzor, I noticed that apollo-server-micro (when used with Zeit’s Now) is reliable.

@bigman73
Copy link

It's always annoying when a module becomes unsupported / unmaintained, but I'd expect a proper announcement on the front page - let users know that end of life is coming so they have time to find alternatives.

@chris-aeviator
Copy link

It's always annoying when a module becomes unsupported / unmaintained, but I'd expect a proper announcement on the front page - let users know that end of life is coming so they have time to find alternatives.

same goes for stale bots so people could react with a 👍 to avoid a stale

@saihaj
Copy link
Collaborator

saihaj commented Feb 19, 2022

Hey @vjsingh @pilatte @chris-aeviator @heymartinadams @bigman73 we @the-guild-org are the new maintainers of this project. We are actively working on v2. The new yoga

  • supports subscriptions using server sent events and requires no additional setup or relies on external dependencies
  • Is framework agnostic so you can use it directly or chose to integrate with your existing setup
  • Supports various serverless/edge providers with no additional setup

Would love to get your feedback on beta release and you can checkout our new docs https://www.graphql-yoga.com (still wip)

@saihaj saihaj closed this as completed Feb 19, 2022
@Urigo
Copy link
Collaborator

Urigo commented Mar 29, 2022

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!

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

8 participants