Yoga v3 Breaking Changes

[zolero]

Hi Yoga Devs,

I'm currently working on projects that needs to be in production soon.
Although these updates the last few months there keeps coming more and more breaking changes, v1 yoga to v2, now v3.

Completely different architecture with Envelop, had to dig into much code to find why my server stops working because of lack of documentation....

When will this stop? Since I can't depend on such library if there keeps coming these changes. Is v4 already in the pipeline or?...
Could someone please tell me, because this is undoable to develop on.

Kind regards,.
Joost

[saihaj]

Roadmaps are posted months in advance when we start planning for new major upgrades. Major upgrades are done for a reason and we do recommend users to upgrade. We do our best to provide migration guides https://the-guild.dev/graphql/yoga-server/docs/migration/migration-from-yoga-v2 for different major version but if something is missing let us know more than happy to assist and simplify migration.

[zolero]

I will elaborate my pain for you a bit.

First of all the implementation of graphql-middleware. Since you guys are moving to a different implementation and binding completely to envelop documentations are outdated for other libraries as well: Graphql Middleware

It took me quiet a while to search for a solution after digging into the code and finally found out that for middleware without to completely having to move to envelop I should use:

plugins: [useGraphQLMiddleware([yupMiddleware])]
Instead of just: middlewares: [yupMiddleware]

Then I encountered quiet some pain using graphql-shield which is created by you guys as well. The documentation shows that Yup can be used for validations. But I almost always encounter "Not Authorised!" on performing yup validations and couldn't find out why because of lack of documentation as well. Till the frustration got so high I was like. What does this graphql-shield anyways. Which is basically not much more then using graphql-middleware itself instead.

Then all the type definitions in TypeScript. renames from and moving from package to other package names: @graphql-yoga/node -> graphql-yoga.

All documentations pretty much for newcomers into the GraphQL field doesn't have a clue to start right now. Anyhow.

My message now: keep this structure for at least a year to come so people can write tutorials, and help others out because this way it is just a pain for everyone.

[n1ru4l]

I understand why this field is moving so fast but instead of binding to a different set of libraries, every 3 to 4 months is just a pain.

When we took over GraphQL Yoga and shaped/transitioned it into something, it was obvious that there will be breaking changes.

If you use open-source software and don't commit to following its updates, you are free to do your research and use another library.
Yoga v2 and v3 were big improvements, and even there the update from v2 to v3 is pretty straightforward.

For me it kind of feels like a fun playground project right now, unfortunately. I understand why this field is moving so fast but instead of binding to a different set of libraries, every 3 to 4 months is just a pain.

I think this argument can easily be countered as we are using Yoga and testing in production with many of our clients and our open-source GraphQL Hive project that serves several billions of requests every month.

[n1ru4l]

It took me quite a while to search for a solution after digging into the code and finally found out that for middleware without to completely having to move to envelop I should use:

This is documented in our upgrade guide already. https://the-guild.dev/graphql/yoga-server/docs/migration/migration-from-yoga-v1#middlewares

[zolero]

It took me quite a while to search for a solution after digging into the code and finally found out that for middleware without to completely having to move to envelop I should use:

This is documented in our upgrade guide already. https://the-guild.dev/graphql/yoga-server/docs/migration/migration-from-yoga-v1#middlewares

Can you guys put this documentation about middlewares into the features list of v3. Since even after spitting into all documentation this v1 to v2 upgrade got completely lost for me after upgrading to v3.

[saihaj]

It took me quiet a while to search for a solution after digging into the code and finally found out that for middleware without to completely having to move to envelop I should use:
plugins: [useGraphQLMiddleware([yupMiddleware])]
Instead of just: middlewares: [yupMiddleware]

Our migrations guide from v1 to v2 included all that information https://the-guild.dev/graphql/yoga-server/v2/migration/migration-from-yoga-v1#middlewares

Then I encountered quiet some pain using graphql-shield which is created by you guys as well. The documentation shows that Yup can be used for validations. But I almost always encounter "Not Authorised!" on performing yup validations and couldn't find out why because of lack of documentation as well. Till the frustration got so high I was like. What does this graphql-shield anyways. Which is basically not much more then using graphql-middleware itself instead.

We recently took over the maintenance of shield. Usage example improvements is something to ask in the repo or here. Now that you have it figured out would love that you help us improve the docs!

Then all the type definitions in TypeScript. renames from and moving from package to other package names: @graphql-yoga/node -> graphql-yoga.

The reasoning for this was was explained in migration docs and our blog post. But regardless you can still use the old package and it would just warn you about deprecation. We do not just remove the package.

All documentations pretty much for newcomers into the GraphQL field doesn't have a clue to start right now. Anyhow.

enlighten me more on this.

[n1ru4l]

Hey, @zolero can you please let us know what specific topics provide issues? We are happy to help you out with the transition.