From 0b4093a7d92fdc651fbb82e7c76b8dff3e6bc9c5 Mon Sep 17 00:00:00 2001
From: heiso <alexandre.moatty@gmail.com>
Date: Mon, 15 Apr 2024 09:19:40 +0200
Subject: [PATCH] fix: fix gh-pages behaviors

---
 web-app/vite.config.ts | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/web-app/vite.config.ts b/web-app/vite.config.ts
index 21bf248..60016ca 100644
--- a/web-app/vite.config.ts
+++ b/web-app/vite.config.ts
@@ -1,5 +1,7 @@
 import { vitePlugin as remix } from '@remix-run/dev'
 import { installGlobals } from '@remix-run/node'
+import { copyFileSync } from 'node:fs'
+import { join } from 'node:path'
 
 import { defineConfig } from 'vite'
 
@@ -16,6 +18,20 @@ export default defineConfig({
     remix({
       ssr: false,
       basename: BASE_PATH,
+      buildEnd(args) {
+        if (!args.viteConfig.isProduction) return
+
+        // When deploying to GitHub Pages, if you navigate from / to another
+        // route and refresh the tab, it will show the default GH Pages 404
+        // page. This happens because GH Pages is not configured to send all
+        // traffic to the index.html where we can load our client-side JS.
+        // To fix this, we can create a 404.html file that contains the same
+        // content as index.html. This way, when the user refreshes the page,
+        // GH Pages will serve our 404.html and everything will work as
+        //expected.
+        const buildPath = args.viteConfig.build.outDir
+        copyFileSync(join(buildPath, 'index.html'), join(buildPath, '404.html'))
+      },
     }),
   ],
 })