v4.11.3

Patch Changes

• #1321 4a1fd6a Thanks @github-actions! - add error codes for new Apollo Client version

v4.11.2

Patch Changes

• #1313 84fb904 Thanks @phryneas! - add error codes for new Apollo Client version

v4.11.1

Patch Changes

• #1303 df0d242 Thanks @jerelmiller! - Fix issue where terminating the client by calling .stop would not disconnect it from devtools making it difficult to track newly created clients.

v4.11.0

Minor Changes

• #1286 11309f3 Thanks @phryneas! - Change transpilation target to create a smaller and more modern DevTools build.

v4.10.1

Patch Changes

• #1287 052f242 Thanks @phryneas! - Move access to the gql helper into the background worker to reduce size of injected JavaScript.

v4.10.0

Minor Changes

• #1281 badb1f9 Thanks @phryneas! - Add the ability for devtools to provide full error and log messages without the need to need to call loadDevMessages or loadErrorMessages.

Patch Changes

• #1293 e417490 Thanks @github-actions! - add error codes for new Apollo Client version

v4.9.1

Patch Changes

• #1278 e886145 Thanks @jerelmiller! - Fix issue with error serialization when sending an error back through the message passing system. Unfortunately the raw error instance was lost in this process. This fix retains the error message when sending error messages in rpc calls.

v4.9.0

Minor Changes

• #1256 28140d8 Thanks @jerelmiller! - Introduce rpc utilities to communicate between the extension scripts. Migrate the call to get client data into the devtools to use the rpc utilities.

v4.8.3

Patch Changes

• #1264 66c05ae Thanks @phryneas! - Enable "@typescript-eslint/consistent-type-imports" lint rule

• #1265 df5300f Thanks @phryneas! - Use relative-CI to monitor build artefact sizes

• #1268 4c98879 Thanks @jerelmiller! - Revert change that removed JSON stringify on the entire set of client data. This is a followup to #1259 which only partially fixed the issue.

v4.8.2

Patch Changes

• #1262 122c3ee Thanks @phryneas! - prevent bundling Apollo Client in the hooks.js build

• #1259 de55e20 Thanks @jerelmiller! - Fix an issue when sending cache data from the browser to the extension. This was particularly problematic when the cache contained URL instances which are not cloneable via the structured clone algorithm