fix(backend): use updated IS_DEV when creating Collections

this was previously using the old path, which resulted in collections always falling back to their default (prod) values, rather than using the expected values in dev
SwitchbackTech · Jan 1, 2025 · c3d40ab · c3d40ab
1 parent a6cb22e
commit c3d40ab
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/packages/backend/src/common/constants/collections.ts b/packages/backend/src/common/constants/collections.ts
@@ -1,4 +1,4 @@
-import { IS_DEV } from "@backend/common/constants/env.constants";
+import { IS_DEV } from "./env.constants";
 
 export const Collections = {
   CALENDARLIST: IS_DEV ? "_dev.calendarlist" : "calendarlist",

diff --git a/packages/backend/src/common/constants/env.constants.ts b/packages/backend/src/common/constants/env.constants.ts
@@ -10,7 +10,7 @@ if (!Object.values(NodeEnv).includes(_nodeEnv)) {
   throw new Error(`Invalid NODE_ENV value: '${_nodeEnv}'`);
 }
 
-const IS_DEV = isDev(_nodeEnv);
+export const IS_DEV = isDev(_nodeEnv);
 
 const EnvSchema = z
   .object({