[Snyk] Upgrade @apollo/client from 3.3.11 to 3.9.0 #1977
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @apollo/client from 3.3.11 to 3.9.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version fixes:
SNYK-JS-APOLLOCLIENT-1085706
Why? Has a fix available, CVSS 5.3
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: @apollo/client
Read more
Patch Changes
67f62e3
Thanks @ jerelmiller! - Release changes fromv3.8.10
Minor Changes
1190aa5
Thanks @ jerelmiller! - Increase the default memory limits forexecuteSelectionSet
andexecuteSelectionSetArray
.Minor Changes
#11424
62f3b6d
Thanks @ phryneas! - Simplify RetryLink, fix potential memory leakHistorically,
RetryLink
would keep avalues
array of all previous values,in case the operation would get an additional subscriber at a later point in time.
In practice, this could lead to a memory leak (#11393) and did not serve any
further purpose, as the resulting observable would only be subscribed to by
Apollo Client itself, and only once - it would be wrapped in a
Concast
beforebeing exposed to the user, and that
Concast
would handle subscribers on itsown.
#11442
4b6f2bc
Thanks @ jerelmiller! - Remove the need to callretain
fromuseLoadableQuery
sinceuseReadQuery
will now retain the query. This means that aqueryRef
that is not consumed byuseReadQuery
within the givenautoDisposeTimeoutMs
will now be auto diposed for you.Thanks to #11412, disposed query refs will be automatically resubscribed to the query when consumed by
useReadQuery
after it has been disposed.#11438
6d46ab9
Thanks @ jerelmiller! - Remove the need to callretain
fromuseBackgroundQuery
sinceuseReadQuery
will now retain the query. This means that aqueryRef
that is not consumed byuseReadQuery
within the givenautoDisposeTimeoutMs
will now be auto diposed for you.Thanks to #11412, disposed query refs will be automatically resubscribed to the query when consumed by
useReadQuery
after it has been disposed.Patch Changes
#11443
ff5a332
Thanks @ phryneas! - Adds a deprecation warning to the HOC and render prop APIs.The HOC and render prop APIs have already been deprecated since 2020,
but we previously didn't have a @ deprecated tag in the DocBlocks.
#11078
14edebe
Thanks @ phryneas! - ObservableQuery: prevent reporting results of previous queries if the variables changed since#11439
33454f0
Thanks @ jerelmiller! - Address bundling issue introduced in #11412 where thereact/cache
internals ended up duplicated in the bundle. This was due to the fact that we had areact/hooks
entrypoint that imported these files along with the newly introducedcreateQueryPreloader
function, which lived outside of thereact/hooks
folder.Minor Changes
#11412
58db5c3
Thanks @ jerelmiller! - Create a newuseQueryRefHandlers
hook that returnsrefetch
andfetchMore
functions for a givenqueryRef
. This is useful to get access to handlers for aqueryRef
that was created bycreateQueryPreloader
or when the handlers for aqueryRef
produced by a different component are inaccessible.const MyComponent({ queryRef }) {
const { refetch, fetchMore } = useQueryRefHandlers(queryRef);
// ...
}
#11410
07fcf6a
Thanks @ sf-twingate! - Allow returningIGNORE
sentinel object fromoptimisticResponse
functions to bail-out from the optimistic update.Consider this example:
const UPDATE_COMMENT = gql
mutation UpdateComment($commentId: ID!, $commentContent: String!) { updateComment(commentId: $commentId, content: $commentContent) { id __typename content } }
;function CommentPageWithData() {
const [mutate] = useMutation(UPDATE_COMMENT);
return (
<Comment
updateComment={({ commentId, commentContent }) =>
mutate({
variables: { commentId, commentContent },
optimisticResponse: (vars, { IGNORE }) => {
if (commentContent === "foo") {
// conditionally bail out of optimistic updates
return IGNORE;
}
return {
updateComment: {
id: commentId,
__typename: "Comment",
content: commentContent,
},
};
},
})
}
/>
);
}
The
IGNORE
sentinel can be destructured from the second parameter in the callback function signature passed tooptimisticResponse
.#11412
58db5c3
Thanks @ jerelmiller! - Add the ability to start preloading a query outside React to begin fetching as early as possible. CallcreateQueryPreloader
to create apreloadQuery
function which can be called to start fetching a query. This returns aqueryRef
which is passed touseReadQuery
and suspended until the query is done fetching.const preloadQuery = createQueryPreloader(client);
const queryRef = preloadQuery(QUERY, { variables, ...otherOptions });
function App() {
return {
<Suspense fallback={<div>Loading</div>}>
<MyQuery />
</Suspense>
}
}
function MyQuery() {
const { data } = useReadQuery(queryRef);
// do something with data
}
#11397
3f7eecb
Thanks @ aditya-kumawat! - Adds a newskipPollAttempt
callback function that's called whenever a refetch attempt occurs while polling. If the function returnstrue
, the refetch is skipped and not reattempted until the next poll interval. This will solve the frequent use-case of disabling polling when the window is inactive.#11435
5cce53e
Thanks @ phryneas! - DeprecatescanonizeResults
.Using
canonizeResults
can result in memory leaks so we generally do not recommend using this option anymore.A future version of Apollo Client will contain a similar feature without the risk of memory leaks.
Patch Changes
#11369
2a47164
Thanks @ phryneas! - Persisted Query Link: improve memory managementWeakCache
instead ofWeakMap
to keep a limited number of hash resultspersistedLink.resetHashCache()
method#10804
221dd99
Thanks @ phryneas! - use WeakMap in React Native with Hermes#11409
2e7203b
Thanks @ phryneas! - Adds an experimentalApolloClient.getMemoryInternals
helperMinor Changes
#11345
1759066a8
Thanks @ phryneas! -QueryManager.inFlightLinkObservables
now uses a strongTrie
as an internal data structure.Warning: requires
@ apollo/experimental-nextjs-app-support
updateIf you are using
@ apollo/experimental-nextjs-app-support
, you will need to update that to at least 0.5.2, as it accesses this internal data structure.#11300
a8158733c
Thanks @ jerelmiller! - Introduces a newuseLoadableQuery
hook. This hook works similarly touseBackgroundQuery
in that it returns aqueryRef
that can be used to suspend a component via theuseReadQuery
hook. It provides a more ergonomic way to load the query during a user interaction (for example when wanting to preload some data) that would otherwise be clunky withuseBackgroundQuery
.function App() {
const [loadQuery, queryRef, { refetch, fetchMore, reset }] =
useLoadableQuery(query, options);
return (
<>
<button onClick={() => loadQuery(variables)}>Load query</button>
<Suspense fallback={<SuspenseFallback />}>
{queryRef && <Child queryRef={queryRef} />}
</Suspense>
</>
);
}
function Child({ queryRef }) {
const { data } = useReadQuery(queryRef);
// ...
}
Patch Changes
#11356
cc4ac7e19
Thanks @ phryneas! - Fix a potential memory leak inFragmentRegistry.transform
andFragmentRegistry.findFragmentSpreads
that would hold on to passed-inDocumentNodes
for too long.#11370
25e2cb431
Thanks @ phryneas! -parse
function: improve memory managementWeakCache
instead ofMap
to keep a limited number of parsed resultsparse.resetCache()
method#11389
139acd115
Thanks @ phryneas! -documentTransform
: useoptimism
andWeakCache
instead of directly storing data on theTrie
#11358
7d939f80f
Thanks @ phryneas! - Fixes a potential memory leak inConcast
that might have been triggered whenConcast
was used outside of Apollo Client.#11344
bd2667619
Thanks @ phryneas! - Add aresetCache
method toDocumentTransform
and hookInMemoryCache.addTypenameTransform
up toInMemoryCache.gc
#11367
30d17bfeb
Thanks @ phryneas! -print
: useWeakCache
instead ofWeakMap
#11385
d9ca4f082
Thanks @ phryneas! - ensuredefaultContext
is also used for mutations and subscriptions#11387
4dce8673b
Thanks @ phryneas! -QueryManager.transformCache
: useWeakCache
instead ofWeakMap
#11371
ebd8fe2c1
Thanks @ phryneas! - Clarify types ofEntityStore.makeCacheKey
.#11355
7d8e18493
Thanks @ phryneas! - InMemoryCache.gc now also triggers FragmentRegistry.resetCaches (if there is a FragmentRegistry)Read more
Read more
Read more
Read more
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs