You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.
Apollo server 3 reaches end of life on October 22nd, 2023. Without using the beta version of TypeGraphQL we cannot upgrade, because they require incompatible GraphQL versions.
We can wait for now, but before the deadline we will need to figure out which is the least bad (probably using the beta version of TypeGraphQL).
The text was updated successfully, but these errors were encountered:
In hindsight, and because I say it too much, you may think I am trolling. But I am serious, we have Next.js, express, and apollo doing the same thing (fetch data from the backend for the client). If one of them becomes deprecated, we can use the other tool that we already have.
If I am being less "trolly", does it matter if it becomes deprecated? As long as it is doing its functionality, does it matter? Or do we need a new feature from Apollo server 4?
Next.js is only on the client. Express is the webserver. Apollo is the GraphQL server. They're completely different tools and all do different things.
does it matter if it becomes deprecated?
It's not being deprecated on October 22nd, 2023, it's going to reach end of life then. This matters because it means they stop providing security fixes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Apollo server 3 reaches end of life on October 22nd, 2023. Without using the beta version of TypeGraphQL we cannot upgrade, because they require incompatible GraphQL versions.
We can wait for now, but before the deadline we will need to figure out which is the least bad (probably using the beta version of TypeGraphQL).
The text was updated successfully, but these errors were encountered: