@luckystack/core 0.8.0 → 0.8.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/CLAUDE.md +4 -3
- package/dist/index.d.ts +6 -1
- package/dist/index.js +12 -3
- package/dist/index.js.map +1 -1
- package/docs/app-bootstrap.md +3 -2
- package/package.json +1 -1
package/docs/app-bootstrap.md
CHANGED
|
@@ -291,9 +291,10 @@ Returns the registered reloader, or `null` when none was supplied (watcher no-op
|
|
|
291
291
|
|
|
292
292
|
`BOOT_KEY_PREFIX` is exported as the single source of truth so `@luckystack/router`'s `bootHandshake.ts` cannot drift.
|
|
293
293
|
|
|
294
|
-
###
|
|
294
|
+
### Runtime mode versus deploy environment
|
|
295
295
|
|
|
296
|
-
|
|
296
|
+
- `resolveRuntimeMode()` returns the validated `NODE_ENV` application mode (`development`, `production` or `test`). `isProductionRuntime()` and `isTestRuntime()` are convenience predicates. Security, route-map, cookie and dev-tool behavior uses this axis.
|
|
297
|
+
- `resolveEnvKey()` returns `process.env.LUCKYSTACK_ENV` ?? `process.env.NODE_ENV` ?? `'development'`. This is only the deploy-topology identity used by boot UUIDs, health attestation, routing and observability labels. A production process may therefore use `LUCKYSTACK_ENV=staging` without enabling development behavior.
|
|
297
298
|
|
|
298
299
|
### `writeBootUuid(envKey?: string): Promise<string>`
|
|
299
300
|
|