From 70c49495aaa566a748d76cb11586daeef3b0ef13 Mon Sep 17 00:00:00 2001
From: Marcos Lilljedahl <marcosnils@gmail.com>
Date: Thu, 24 Mar 2022 15:55:24 -0300
Subject: [PATCH] Add BrowserOnly component to avoid SSG errors

Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
---
 docs/core-concepts/1203-client.md      | 7 ++++++-
 docs/getting-started/1200-local-dev.md | 6 ++++++
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/docs/core-concepts/1203-client.md b/docs/core-concepts/1203-client.md
index 78151611..80afc27a 100644
--- a/docs/core-concepts/1203-client.md
+++ b/docs/core-concepts/1203-client.md
@@ -31,8 +31,11 @@ You can use a local socket in an action:
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
+import BrowserOnly from '@docusaurus/BrowserOnly';
 
-<Tabs defaultValue={window.navigator.userAgent.indexOf('Win') != -1 ? 'windows': 'unix'} groupId="client-env">
+<BrowserOnly>
+  {() =>
+<Tabs defaultValue={ window.navigator.userAgent.indexOf('Win') != -1 ? 'windows': 'unix'} groupId="client-env">
 
 <TabItem value="unix" label="Linux/macOS">
 
@@ -48,6 +51,8 @@ import TabItem from '@theme/TabItem';
 
 </TabItem>
 </Tabs>
+  }
+</BrowserOnly>
 
 ## Environment variables
 
diff --git a/docs/getting-started/1200-local-dev.md b/docs/getting-started/1200-local-dev.md
index 19e2f78b..f5ebb669 100644
--- a/docs/getting-started/1200-local-dev.md
+++ b/docs/getting-started/1200-local-dev.md
@@ -11,7 +11,10 @@ This guide shows you the Dagger way.
 Within 5 minutes, you will have a local CI/CD loop and run your first test & build pipeline.
 
 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';
+import BrowserOnly from '@docusaurus/BrowserOnly';
 
+<BrowserOnly>
+{() =>
 <Tabs defaultValue={
  window.navigator.userAgent.indexOf('Linux') != -1 ? 'linux':
  window.navigator.userAgent.indexOf('Win') != -1 ? 'windows':
@@ -275,6 +278,9 @@ It becomes even more obvious when the change is not as straightforward as knowin
 </TabItem>
 
 </Tabs>
+}
+
+</BrowserOnly>
 
 :::tip
 Now that we are comfortable with our local CI/CD loop, let us configure a remote CI environment in the second part.