@spinajs/configuration 2.0.529 → 2.0.531

package/lib/cjs/config/configuration.d.ts

@@ -1,3 +1,30 @@
+/**
+ * The single source of truth for "which environment am I running as".
+ *
+ * Derived from the SAME value that selects the config files - `APP_ENV`, falling back to
+ * `NODE_ENV` - and run through the SAME normalizer, so a guard reading these flags and the config
+ * that was actually loaded can never disagree. Reading `NODE_ENV` directly, as this used to,
+ * disagreed in two ways:
+ *
+ *  - A container may pin `NODE_ENV=production` so npm installs production dependencies, and then
+ *    distinguish its stacks with `APP_ENV`. Such a dev container reported production.
+ *  - Only the spelling `production` matched, so `APP_ENV=prod` - which `normalizeEnvironment` maps
+ *    onto the prod config suffix - reported false.
+ *
+ * Both are fail-open for consumers that guard on this: the http package hides error detail on
+ * production, and the email package refuses recipient redirection there.
+ *
+ * These stay ordinary configuration values, so an app may override them in its own config - that
+ * is the point of deciding it here rather than re-deriving it at each call site.
+ *
+ * @param env - process.env, taken as an argument so the derivation is testable without reloading
+ *              the module
+ */
+export declare function buildEnvironmentFlags(env: NodeJS.ProcessEnv): {
+    isDevelopment: boolean;
+    isProduction: boolean;
+    isLocal: boolean;
+};
 declare const config: {
     configuration: {
         isDevelopment: boolean;

package/lib/cjs/config/configuration.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"configuration.d.ts","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":"AAAA,QAAA,MAAM,MAAM;IACV,aAAa;QACX,aAAa;QACb,YAAY;QACZ,OAAO;;IAGT,GAAG;QACD,IAAI;QACJ,OAAO;;CAEV,CAAC;eAEa,MAAM"}
+{"version":3,"file":"configuration.d.ts","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,qBAAqB,CAAC,GAAG,EAAE,MAAM,CAAC,UAAU;IAYxD,aAAa;IACb,YAAY;IACZ,OAAO;EAEV;AAED,QAAA,MAAM,MAAM;IACV,aAAa;;;;;IAEb,GAAG;QACD,IAAI;QACJ,OAAO;;CAEV,CAAC;eAEa,MAAM"}

package/lib/cjs/config/configuration.js

@@ -1,15 +1,51 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.buildEnvironmentFlags = buildEnvironmentFlags;
+const configuration_common_1 = require("@spinajs/configuration-common");
+/**
+ * The single source of truth for "which environment am I running as".
+ *
+ * Derived from the SAME value that selects the config files - `APP_ENV`, falling back to
+ * `NODE_ENV` - and run through the SAME normalizer, so a guard reading these flags and the config
+ * that was actually loaded can never disagree. Reading `NODE_ENV` directly, as this used to,
+ * disagreed in two ways:
+ *
+ *  - A container may pin `NODE_ENV=production` so npm installs production dependencies, and then
+ *    distinguish its stacks with `APP_ENV`. Such a dev container reported production.
+ *  - Only the spelling `production` matched, so `APP_ENV=prod` - which `normalizeEnvironment` maps
+ *    onto the prod config suffix - reported false.
+ *
+ * Both are fail-open for consumers that guard on this: the http package hides error detail on
+ * production, and the email package refuses recipient redirection there.
+ *
+ * These stay ordinary configuration values, so an app may override them in its own config - that
+ * is the point of deciding it here rather than re-deriving it at each call site.
+ *
+ * @param env - process.env, taken as an argument so the derivation is testable without reloading
+ *              the module
+ */
+function buildEnvironmentFlags(env) {
+    // `?? 'development'` mirrors FrameworkConfiguration.load(), which resolves
+    // `Env ?? APP_ENV ?? NODE_ENV ?? 'development'`. Without it a bare process would fall through to
+    // normalizeEnvironment's own default of production and call a developer's laptop prod.
+    //
+    // An explicitly EMPTY APP_ENV is deliberately NOT caught by that default: `??` tests only
+    // null/undefined, so `APP_ENV=` reaches normalizeEnvironment, which resolves it to production -
+    // and such a deployment really does load its prod config. The flag agrees rather than papering
+    // over it.
+    const environment = (0, configuration_common_1.normalizeEnvironment)(env.APP_ENV ?? env.NODE_ENV ?? 'development');
+    return {
+        isDevelopment: environment === 'dev',
+        isProduction: environment === 'prod',
+        isLocal: environment === 'local',
+    };
+}
 const config = {
-    configuration: {
-        isDevelopment: process.env.NODE_ENV === 'development',
-        isProduction: process.env.NODE_ENV === 'production',
-        isLocal: process.env.NODE_ENV === 'local'
-    },
+    configuration: buildEnvironmentFlags(process.env),
     app: {
-        name: "spinajs",
-        version: "1.0.0"
-    }
+        name: 'spinajs',
+        version: '1.0.0',
+    },
 };
 exports.default = config;
 //# sourceMappingURL=configuration.js.map

package/lib/cjs/config/configuration.js.map

@@ -1 +1 @@
-{"version":3,"file":"configuration.js","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":";;AAAA,MAAM,MAAM,GAAG;IACb,aAAa,EAAE;QACb,aAAa,EAAE,OAAO,CAAC,GAAG,CAAC,QAAQ,KAAK,aAAa;QACrD,YAAY,EAAE,OAAO,CAAC,GAAG,CAAC,QAAQ,KAAK,YAAY;QACnD,OAAO,EAAG,OAAO,CAAC,GAAG,CAAC,QAAQ,KAAK,OAAO;KAC3C;IAED,GAAG,EAAE;QACH,IAAI,EAAE,SAAS;QACf,OAAO,EAAE,OAAO;KACjB;CACF,CAAC;kBAEa,MAAM"}
+{"version":3,"file":"configuration.js","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":";;;AAAA,wEAAqE;AAErE;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,+BAAsC,GAAsB;IAC1D,2EAA2E;IAC3E,iGAAiG;IACjG,uFAAuF;IACvF,EAAE;IACF,0FAA0F;IAC1F,gGAAgG;IAChG,+FAA+F;IAC/F,WAAW;IACX,MAAM,WAAW,GAAG,IAAA,2CAAoB,EAAC,GAAG,CAAC,OAAO,IAAI,GAAG,CAAC,QAAQ,IAAI,aAAa,CAAC,CAAC;IAEvF,OAAO;QACL,aAAa,EAAE,WAAW,KAAK,KAAK;QACpC,YAAY,EAAE,WAAW,KAAK,MAAM;QACpC,OAAO,EAAE,WAAW,KAAK,OAAO;KACjC,CAAC;AACJ,CAAC;AAED,MAAM,MAAM,GAAG;IACb,aAAa,EAAE,qBAAqB,CAAC,OAAO,CAAC,GAAG,CAAC;IAEjD,GAAG,EAAE;QACH,IAAI,EAAE,SAAS;QACf,OAAO,EAAE,OAAO;KACjB;CACF,CAAC;kBAEa,MAAM"}

package/lib/mjs/config/configuration.d.ts

@@ -1,3 +1,30 @@
+/**
+ * The single source of truth for "which environment am I running as".
+ *
+ * Derived from the SAME value that selects the config files - `APP_ENV`, falling back to
+ * `NODE_ENV` - and run through the SAME normalizer, so a guard reading these flags and the config
+ * that was actually loaded can never disagree. Reading `NODE_ENV` directly, as this used to,
+ * disagreed in two ways:
+ *
+ *  - A container may pin `NODE_ENV=production` so npm installs production dependencies, and then
+ *    distinguish its stacks with `APP_ENV`. Such a dev container reported production.
+ *  - Only the spelling `production` matched, so `APP_ENV=prod` - which `normalizeEnvironment` maps
+ *    onto the prod config suffix - reported false.
+ *
+ * Both are fail-open for consumers that guard on this: the http package hides error detail on
+ * production, and the email package refuses recipient redirection there.
+ *
+ * These stay ordinary configuration values, so an app may override them in its own config - that
+ * is the point of deciding it here rather than re-deriving it at each call site.
+ *
+ * @param env - process.env, taken as an argument so the derivation is testable without reloading
+ *              the module
+ */
+export declare function buildEnvironmentFlags(env: NodeJS.ProcessEnv): {
+    isDevelopment: boolean;
+    isProduction: boolean;
+    isLocal: boolean;
+};
 declare const config: {
     configuration: {
         isDevelopment: boolean;

package/lib/mjs/config/configuration.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"configuration.d.ts","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":"AAAA,QAAA,MAAM,MAAM;IACV,aAAa;QACX,aAAa;QACb,YAAY;QACZ,OAAO;;IAGT,GAAG;QACD,IAAI;QACJ,OAAO;;CAEV,CAAC;eAEa,MAAM"}
+{"version":3,"file":"configuration.d.ts","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,qBAAqB,CAAC,GAAG,EAAE,MAAM,CAAC,UAAU;IAYxD,aAAa;IACb,YAAY;IACZ,OAAO;EAEV;AAED,QAAA,MAAM,MAAM;IACV,aAAa;;;;;IAEb,GAAG;QACD,IAAI;QACJ,OAAO;;CAEV,CAAC;eAEa,MAAM"}

package/lib/mjs/config/configuration.js

@@ -1,13 +1,48 @@
+import { normalizeEnvironment } from '@spinajs/configuration-common';
+/**
+ * The single source of truth for "which environment am I running as".
+ *
+ * Derived from the SAME value that selects the config files - `APP_ENV`, falling back to
+ * `NODE_ENV` - and run through the SAME normalizer, so a guard reading these flags and the config
+ * that was actually loaded can never disagree. Reading `NODE_ENV` directly, as this used to,
+ * disagreed in two ways:
+ *
+ *  - A container may pin `NODE_ENV=production` so npm installs production dependencies, and then
+ *    distinguish its stacks with `APP_ENV`. Such a dev container reported production.
+ *  - Only the spelling `production` matched, so `APP_ENV=prod` - which `normalizeEnvironment` maps
+ *    onto the prod config suffix - reported false.
+ *
+ * Both are fail-open for consumers that guard on this: the http package hides error detail on
+ * production, and the email package refuses recipient redirection there.
+ *
+ * These stay ordinary configuration values, so an app may override them in its own config - that
+ * is the point of deciding it here rather than re-deriving it at each call site.
+ *
+ * @param env - process.env, taken as an argument so the derivation is testable without reloading
+ *              the module
+ */
+export function buildEnvironmentFlags(env) {
+    // `?? 'development'` mirrors FrameworkConfiguration.load(), which resolves
+    // `Env ?? APP_ENV ?? NODE_ENV ?? 'development'`. Without it a bare process would fall through to
+    // normalizeEnvironment's own default of production and call a developer's laptop prod.
+    //
+    // An explicitly EMPTY APP_ENV is deliberately NOT caught by that default: `??` tests only
+    // null/undefined, so `APP_ENV=` reaches normalizeEnvironment, which resolves it to production -
+    // and such a deployment really does load its prod config. The flag agrees rather than papering
+    // over it.
+    const environment = normalizeEnvironment(env.APP_ENV ?? env.NODE_ENV ?? 'development');
+    return {
+        isDevelopment: environment === 'dev',
+        isProduction: environment === 'prod',
+        isLocal: environment === 'local',
+    };
+}
 const config = {
-    configuration: {
-        isDevelopment: process.env.NODE_ENV === 'development',
-        isProduction: process.env.NODE_ENV === 'production',
-        isLocal: process.env.NODE_ENV === 'local'
-    },
+    configuration: buildEnvironmentFlags(process.env),
     app: {
-        name: "spinajs",
-        version: "1.0.0"
-    }
+        name: 'spinajs',
+        version: '1.0.0',
+    },
 };
 export default config;
 //# sourceMappingURL=configuration.js.map

package/lib/mjs/config/configuration.js.map

@@ -1 +1 @@
-{"version":3,"file":"configuration.js","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,GAAG;IACb,aAAa,EAAE;QACb,aAAa,EAAE,OAAO,CAAC,GAAG,CAAC,QAAQ,KAAK,aAAa;QACrD,YAAY,EAAE,OAAO,CAAC,GAAG,CAAC,QAAQ,KAAK,YAAY;QACnD,OAAO,EAAG,OAAO,CAAC,GAAG,CAAC,QAAQ,KAAK,OAAO;KAC3C;IAED,GAAG,EAAE;QACH,IAAI,EAAE,SAAS;QACf,OAAO,EAAE,OAAO;KACjB;CACF,CAAC;AAEF,eAAe,MAAM,CAAC"}
+{"version":3,"file":"configuration.js","sourceRoot":"","sources":["../../../src/config/configuration.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,oBAAoB,EAAE,MAAM,+BAA+B,CAAC;AAErE;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,qBAAqB,CAAC,GAAsB;IAC1D,2EAA2E;IAC3E,iGAAiG;IACjG,uFAAuF;IACvF,EAAE;IACF,0FAA0F;IAC1F,gGAAgG;IAChG,+FAA+F;IAC/F,WAAW;IACX,MAAM,WAAW,GAAG,oBAAoB,CAAC,GAAG,CAAC,OAAO,IAAI,GAAG,CAAC,QAAQ,IAAI,aAAa,CAAC,CAAC;IAEvF,OAAO;QACL,aAAa,EAAE,WAAW,KAAK,KAAK;QACpC,YAAY,EAAE,WAAW,KAAK,MAAM;QACpC,OAAO,EAAE,WAAW,KAAK,OAAO;KACjC,CAAC;AACJ,CAAC;AAED,MAAM,MAAM,GAAG;IACb,aAAa,EAAE,qBAAqB,CAAC,OAAO,CAAC,GAAG,CAAC;IAEjD,GAAG,EAAE;QACH,IAAI,EAAE,SAAS;QACf,OAAO,EAAE,OAAO;KACjB;CACF,CAAC;AAEF,eAAe,MAAM,CAAC"}