@apollo/client
4.3.5 · 19 Oct 2026MIT5.3M / weekRepositoryHomepagenpmAtom feed
Upgrading @apollo/client from 4.3.2 to 4.3.5
3 releases in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 9
- fixes
Release by release
- fixed
Fix an issue where custom scalar values that are not JSON-serializable caused errors. These values are properly serialized when used as input for
variablesor when used as a key field value so that cache writes and calls tocache.identifysucceed. - fixed
Require the
variablesoption inuseFragmentwhen the fragment has required variables. This matches the behavior ofuseSuspenseFragmentand the query hooks. - fixed
Parse custom scalar fields in subscription results when using the
no-cachefetch policy.
- fixed
- fixed
Fix an issue where a list field selected more than once with different selection sets lost the fields that only one of the selections included while a
@deferboundary elsewhere in the query was still pending when using theGraphQL17Alpha9Handler. The results of all selections of the list field are now merged. - fixed
Fixed a bug where
streamFieldInfomight not have been passed into custom merge functions for - fixed
Fix
Missing fielderrors being logged when writing@deferresults where a parent field is selected both inside and outside of a deferred fragment. Fields whose@deferboundary has not been delivered from the network are no longer reported as missing. - fixed
Unregister the watch when an immediate
cache.watchbroadcast throws. Previously the watch was added to the cache before its first read, and a read that threw left the watch registered while the caller never received the unsubscribe function, so it could not be removed and every later broadcast ran into the same failing read. - fixed
Defer20220824Handler: fix a situation wheredataStatewould show up ascompletedwith incremental errors instead of stayingstreaming.
- fixed
- fixed
Fix a memory leak in
isDeferredFragment/isStreamField
- fixed