Releases: apollographql/apollo-client-devtools
v4.8.1
Patch Changes
-
#1245
cb22c6f
Thanks @jerelmiller! - Don'tJSON.stringify
the Apollo Client instance data before sending it in the message payload when communicating between the various parts of the devtools extension. This was mostly redundant since message passing already relies on the structured clone algorithm. -
#1249
a36f59d
Thanks @jerelmiller! - Merge the tabRelay script with the tab script by extracting the body of the Promise callback into tab.ts. This behavior was no longer needed.
v4.8.0
Minor Changes
- #1232
8ce6fef
Thanks @jerelmiller! - Changes the tab injection mechanism for better compatibility with websites that might have issues with hydration mismatches when using the old injection mechanism.
v4.7.0
Minor Changes
-
#1226
7c89199
Thanks @jerelmiller! - Rework the message passing between all areas of the devtools to provide more stability. In particular, the message passing has changed in the following ways:- All messages now contain a
source
property set toapollo-client-devtools
. This avoids potential clashes with events emitted fromwindow
that had nothing to do with the devtools. This also means that apps or other utilities that listen to messages onwindow
know where the message originates. - Strengthen the relationship in the background scripts between the tab and devtools ports.
- Add much better type safety for all messages sent through the various areas of the devtools.
- All messages now contain a
Patch Changes
- #1228
41db9be
Thanks @jerelmiller! - Enable strict tsconfig
v4.6.0
Minor Changes
- #1225
b63c467
Thanks @jerelmiller! - Migrate the chrome extension to manifest v3.
v4.5.0
Minor Changes
-
#1220
efcd415
Thanks @jerelmiller! - Change the devtools behavior to always create a panel regardless of whether an Apollo Client instance can be found. This ensures the panel can at least be reached even if the inter-extension communiation is flaky, or our client detection mechanism is buggy. This should help alleviate the large number of reports that the devtools is simply broken.To provide more helpful feedback during usage, status messages are now displayed to show that the devtools is actively trying to locate the client. When a client instance is not found, a helpful dialog is now shown with troubleshooting steps to try and help resolve the issue.
v4.4.3
Patch Changes
- #1202
a36a3b7
Thanks @jerelmiller! - Remove action-hook-fired event that was triggered with nothing listening. This change meant that the__actionHookForDevTools
callback did nothing. This has now been disabled to avoid adding an extraonBroadcast
listener on the client.
v4.4.2
Patch Changes
-
#1198
5d75744
Thanks @jerelmiller! - Stop broadcasting messages that aren't listened to by the extension.client-found
panel-open
panel-closed
-
#1197
7e9f4ec
Thanks @jerelmiller! - Fix font size of code blocks to match new Apollo design system.
v4.4.1
Patch Changes
- #1194
e3118d1
Thanks @jerelmiller! - Use icons from new@apollo/icons
package.
v4.4.0
Minor Changes
- #1180
3a5d8dd
Thanks @jerelmiller! - Update to new Apollo branding and color scheme. Includes layout improvements and reduces some information redundancy.
v4.3.1
Patch Changes
- #1169
5a36ab4
Thanks @alessbell! - Revert change to script injection approach