Remove next-runtime-env

It was only used in getSiteConfigs() which is never called on the client-side
vivid-planet · Jul 31, 2024 · 9f76ef9 · 9f76ef9
1 parent 96173ce
commit 9f76ef9
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 18 deletions.
diff --git a/site/package-lock.json b/site/package-lock.json
diff --git a/site/package.json b/site/package.json
@@ -29,7 +29,6 @@
         "cache-manager": "^5.6.1",
         "graphql": "^15.0.0",
         "next": "^14.2.0",
-        "next-runtime-env": "^3.2.2",
         "react": "^18.2.0",
         "react-dom": "^18.2.0",
         "react-intl": "^6.0.0",

diff --git a/site/src/config.ts b/site/src/config.ts
@@ -1,5 +1,3 @@
-import { env } from "next-runtime-env";
-
 import { ContentScope, PublicSiteConfig as SiteConfig } from "../../site-configs.d";
 
 export type { SiteConfig };
@@ -20,7 +18,7 @@ export function getSiteConfigForScope(scope: ContentScope) {
 let siteConfigs: SiteConfig[];
 export function getSiteConfigs() {
     if (!siteConfigs) {
-        const json = typeof window === "undefined" ? process.env.NEXT_PUBLIC_SITE_CONFIGS : env("NEXT_PUBLIC_SITE_CONFIGS");
+        const json = process.env.NEXT_PUBLIC_SITE_CONFIGS;
         if (!json) throw new Error("process.env.NEXT_PUBLIC_SITE_CONFIGS must be set.");
         siteConfigs = JSON.parse(json) as SiteConfig[];
     }