temporarily use plain process.env in instrumentation:

tracked: t3-oss/t3-env#287
shawnmclean · Nov 27, 2024 · 6edfc0d · 6edfc0d
1 parent 462d096
commit 6edfc0d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/apps/sovoli.com/src/env.ts b/apps/sovoli.com/src/env.ts
@@ -39,7 +39,6 @@ export const env = createEnv({
     PORT: process.env.PORT,
     VERCEL_PROJECT_PRODUCTION_URL: process.env.VERCEL_PROJECT_PRODUCTION_URL,
     NEXT_PUBLIC_SUPABASE_URL: process.env.NEXT_PUBLIC_SUPABASE_URL,
-    // NEXT_PUBLIC_CLIENTVAR: process.env.NEXT_PUBLIC_CLIENTVAR,
   },
   skipValidation:
     !!process.env.CI || process.env.npm_lifecycle_event === "lint",

diff --git a/apps/sovoli.com/src/instrumentation.ts b/apps/sovoli.com/src/instrumentation.ts
@@ -1,7 +1,9 @@
+// eslint-disable-next-line @typescript-eslint/no-unused-vars -- would like to use this if it works, tracked here: https://github.com/t3-oss/t3-env/issues/287
 import { env } from "./env";
 
 export async function register() {
-  if (env.NEXT_RUNTIME === "nodejs") {
+  // eslint-disable-next-line turbo/no-undeclared-env-vars, no-restricted-properties
+  if (process.env.NEXT_RUNTIME === "nodejs") {
     console.log("instrumentation registering");
     await import("./instrumentation.node");
   }