graphql-yoga VS nuxt3-fullstack

We have migration guide try it out! We can't wait answer your questions and get your feedback on how we can make GraphQL Yoga even more better!

Within our GraphQL Yoga monorepository we have a subscription package which includes a maintained (and fully TypeScript typed) PubSub implementation. https://github.com/dotansimha/graphql-yoga/tree/main/packages/subscription / https://the-guild.dev/graphql/yoga-server/v3/features/subscriptions#pubsub

It's easy to do with a Serverless Function and with GraphQL Yoga.

And since Yoga server works perfectly with Envelop plugins, a verity of error handling and security plugins are available on the plugin hub

In today's article we are going to create a GraphQL api using the Koa framework together with the GraphQL Yoga library and Pothos. In addition, we will use Kysely, which is a query builder entirely written in TypeScript.

I want to share my approach to handling errors in GraphQL resolvers (I use GraphQL Yoga on the server-side) and pass them to the frontend side (where I use Svelte + @urql/svelte).

Last, in case you just want a simple GraphQL server where you don’t have to setup anything and subscriptions work out of the box (using SSE), you might wanna check out GraphQL Yoga v2 (Disclaimer: I am maintaining this library).

What is your server setup like? Have you tried the latest GraphQL Yoga ? It has everything configured OOTB including subscriptions.

Not that I know of. But here are a few things that may be of interest.

Redwood's GraphQL API is built on Yoga (we collaborate tightly with The Guild) — https://www.graphql-yoga.com You just need a GraphQL Client, which The Guild already has an option ready for you https://apollo-angular.com (Note: Apollo or other clients fine as well.)

Here's an example "How To" about connecting Next (React) with Redwood: https://community.redwoodjs.com/t/how-to-connect-a-next-js-f...

I'm a co-founder of Redwood and help lead the project so I can say as a matter of fact we a highly collaborative and enjoy (and support) exploratory projects. It's a priority for us to better demonstrate the power of Redwood's API through examples. If you'd be interested in digging in collaboratively with the community, I can help connect the dots. Just kick things off over here and tag me @thedavidprice: https://community.redwoodjs.com

No pressure at all! Just wanted you to know the invitation is open. Anytime.

Nuxt3 is universal so it can target node, serverless, etc. AFAIK Next can also target serverless. So the issue with SSE is related to the underlying http server (unjs/h3) I think. That’s why I was looking at WS since I got this working with GraphQL Helix / Urql (repository here for those interested.. it has auth/Prisma/FormKit/Tailwind).