chore: updates apollo-client and graphql to latest#594
Merged
Conversation
jeremymwells
approved these changes
Jun 16, 2026
KLongmuirHD
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@apollo/clientfrom^4.1.9→^4.2.3graphqlfrom^16.13.2→^17.0.0(Apollo 4.2.x declares support for both^16and^17)apollo.client.tsto satisfy Apollo 4.2.x's new type-safety requirementsWhy the type augmentations are needed
Apollo Client 4.2 introduced two breaking type-system changes:
1.
DeclareDefaultOptions— required before usingerrorPolicyas a defaultApollo 4.2 uses a type-guard pattern that makes
errorPolicyindefaultOptionsresolve to an error-message string type unless explicitly declared via module augmentation. Without this, thecreateApollofactory produced aTS2322error.2.
SignatureStyle— modern vs. classic call signaturesDeclaring non-empty
DeclareDefaultOptionsinterfaces causes Apollo to automatically switchclient.mutateandclient.queryto the new "modern" signature style, which:TypedDocumentNodeand type inference<TData, TVariables>type argumentsSince all existing call sites use explicit generics against plain
DocumentNode, we pinsignatureStyle: 'classic'inTypeOverridesto preserve backward-compatible behavior.Test plan
npm run typecheckpasses with zero errorsnpm testpasseshd scancompletes successfully