From abc57ca3c3f3f13838316a931341da9f6094fa41 Mon Sep 17 00:00:00 2001
From: Adrien Crivelli <adrien.crivelli@gmail.com>
Date: Thu, 2 May 2024 17:09:25 +0700
Subject: [PATCH] No need for `connectToDevTools: false` anymore

Because ApolloClient is created outside of NgZone
---
 .../performance/server-side-rendering.mdx     | 27 -------------------
 1 file changed, 27 deletions(-)

diff --git a/website/src/pages/docs/performance/server-side-rendering.mdx b/website/src/pages/docs/performance/server-side-rendering.mdx
index e75874fee..a8d4239eb 100644
--- a/website/src/pages/docs/performance/server-side-rendering.mdx
+++ b/website/src/pages/docs/performance/server-side-rendering.mdx
@@ -174,33 +174,6 @@ apollo.create({
 });
 ```
 
-## Using Apollo DevTools
-
-The current Apollo client implementation supports a chrome dev tools plugin for troubleshooting
-queries. When using Apollo with SSR in a development environment, the attempts to connect to the
-plugin can cause the server to hang for about 10s.
-
-To avoid this, you can set the `connectToDevTools` option to `false` as below:
-
-```ts
-// When providing options
-{
-  provide: APOLLO_OPTIONS,
-  useFactory: () {
-    return {
-      connectToDevTools: false
-      // ...
-    };
-  },
-},
-
-// Or when creating the client
-apollo.create({
-  connectToDevTools: false
-  // ...
-})
-```
-
 ## Best Practices
 
 You saw how to use Server-Side Rendering and Store Rehydration in your application, but you will