chore: replace NODE_ENV at build time

With react, it tries to read from process.env, but this fails on mobile leading to the plugin failing to load. By replacing this at build-time, we can sidestep this issue.
jamiebrynes7 · Mar 13, 2024 · beb3550 · beb3550
1 parent 6cb50f8
commit beb3550
Show file tree

Hide file tree

Showing 3 changed files with 55 additions and 0 deletions.
diff --git a/plugin/package-lock.json b/plugin/package-lock.json
diff --git a/plugin/package.json b/plugin/package.json
@@ -27,6 +27,7 @@
   },
   "devDependencies": {
     "@biomejs/biome": "^1.5.3",
+    "@rollup/plugin-replace": "^5.0.5",
     "@sveltejs/vite-plugin-svelte": "^3.0.2",
     "@testing-library/jest-dom": "^6.4.2",
     "@testing-library/react": "^14.2.1",

diff --git a/plugin/vite.config.mts b/plugin/vite.config.mts
@@ -3,6 +3,7 @@ import { svelte } from "@sveltejs/vite-plugin-svelte";
 import { viteStaticCopy } from "vite-plugin-static-copy";
 import path, { resolve } from "path";
 import { loadEnv } from "vite";
+import replace from '@rollup/plugin-replace';
 
 function getOutDir(): string | undefined {
   const env = loadEnv("prod", process.cwd());
@@ -31,6 +32,9 @@ export default defineConfig({
         },
       ],
     }),
+    replace({
+      "process.env.NODE_ENV": JSON.stringify(process.env.NODE_ENV),
+    })
   ],
   build: {
     // We aren't building a website, so we build in library mode