resolved merge conflicts in package.json

Author: dvorakjt

.github/workflows/publish-to-wiki.yml

@@ -0,0 +1,41 @@
+name: Publish to Wiki
+
+on:
+  push:
+    branches:
+      - development
+
+concurrency:
+  group: wiki
+  cancel-in-progress: true
+
+permissions:
+  contents: write
+
+jobs:
+  wiki:
+    name: Publish to Wiki
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Source
+        uses: actions/checkout@v4
+        with:
+          repository: ${{github.repository}}
+          path: ${{github.repository}}
+
+      - name: Checkout Wiki
+        uses: actions/checkout@v4
+        with:
+          repository: ${{github.repository}}.wiki
+          path: ${{github.repository}}.wiki
+
+      - name: Push to Wiki
+        run: |
+          set -e
+          find "$GITHUB_WORKSPACE/${{github.repository}}.wiki" -name "*.md" -delete
+          cd $GITHUB_WORKSPACE/${{github.repository}}.wiki
+          cp -r $GITHUB_WORKSPACE/${{github.repository}}/wiki/* .
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+          git add .
+          git diff-index --quiet HEAD || git commit -m "update wiki" && git push

.github/workflows/run-unit-tests.yml

@@ -30,7 +30,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
-          node-version: '18.x'
+          version: latest
       - uses: supabase/setup-cli@v1
         with:
           version: latest

CONTRIBUTING.md

@@ -1,23 +1,25 @@
 /*
-  Hides warning messages due to multiple Supabase clients being created for tests. 
-  Supabase prints a warning message to the console because multiple Supabase 
-  clients existing in the same browser context could result in unexpected 
-  behavior. Multiple Supabase clients is often a necessity for testing, so this 
-  warning message is hidden.
+  Hide warning messages that are irrelevant to the testing environment, re:
+  
+  - The creation of multiple Supabase clients. Supabase prints a warning message 
+    to the console because the existence of multiple Supabase clients in the 
+    same browsing context could result in unexpected behavior.
+
+  - Google Analytics not initialized.
 */
 const { warn } = console;
 
 const actualWarn = (message, ...optionalParams) => {
   warn.call(console, message, ...optionalParams);
 };
 
+const warningsToIgnore = [
+  'Multiple GoTrueClient instances detected in the same browser context.',
+  '@next/third-parties: GA has not been initialized',
+];
+
 console.warn = (message, ...optionalParams) => {
-  if (
-    message &&
-    message.includes(
-      'Multiple GoTrueClient instances detected in the same browser context.',
-    )
-  ) {
+  if (message && warningsToIgnore.some(warning => message.includes(warning))) {
     return;
   }