@apollo/client 3.8.0-rc.0

v3.8.0-rc.0

on Node.js Yarn

3.8.0-rc.0

Minor Changes

• #11058 89bf33c42 Thanks @phryneas! - (Batch)HttpLink: Propagate AbortErrors to the user when a user-provided signal is passed to the link. Previously, these links would swallow all AbortErrors, potentially causing queries and mutations to never resolve. As a result of this change, users are now expected to handle AbortErrors when passing in a user-provided signal.

• #11040 125ef5b2a Thanks @phryneas! - HttpLink/BatchHttpLink: Abort the AbortController signal more granularly.
  Before this change, when HttpLink/BatchHttpLink created an AbortController
  internally, the signal would always be .aborted after the request was completed. This could cause issues with Sentry Session Replay and Next.js App Router Cache invalidations, which just replayed the fetch with the same options - including the cancelled AbortSignal.

  With this change, the AbortController will only be .abort()ed by outside events,
  not as a consequence of the request completing.

Patch Changes

• #11053 c0ca70720 Thanks @phryneas! - Add SuspenseCache as a lazy hidden property on ApolloClient.
  This means that SuspenseCache is now an implementation details of Apollo Client
  and you no longer need to manually instantiate it and no longer need to pass it
  into ApolloProvider.
  Trying to instantiate a SuspenseCache instance in your code will now throw an
  error.

  Migration:

  -import { SuspenseCache } from '@apollo/client';
  
  -const suspenseCache = new SuspenseCache();
  
  -<ApolloProvider client={client} suspenseCache={suspenseCache} />;
  +<ApolloProvider client={client} />;