@luckystack/core 0.4.1 → 0.5.0

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 CHANGED
@@ -7,6 +7,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.5.0] - 2026-07-11
11
+
12
+ ### Changed
13
+
14
+ - **`@prisma/client` is now an OPTIONAL peer dependency** (ADR 0020, the ORM
15
+ choice). npm no longer auto-installs it; scaffolded projects get it via the
16
+ template's direct dependency when `orm: 'prisma'`. Non-scaffolded projects
17
+ that relied on peer auto-install must add `@prisma/client` to their own
18
+ `package.json`. The same demotion applies in `@luckystack/api`, `devkit`,
19
+ `server`, `sync`, and `login`.
20
+ - `@prisma/client` left the static-import position in `db.ts`: the default
21
+ resolver now lazy-`require()`s it on first access. When it is absent AND no
22
+ client was registered, DB access throws an actionable error pointing at
23
+ `luckystack/core/clients.ts` instead of a bare `ERR_MODULE_NOT_FOUND` at boot.
24
+
25
+ ### Added
26
+
27
+ - `isPrismaClientResolvable()` — is a generated `@prisma/client` present?
28
+ - `registerDbHealthCheck` / `getDbHealthCheck` / `isDbHealthCheckRegistered` /
29
+ `resetDbHealthCheckForTests` (+ types `DbHealthCheck`, `DbHealthResult`) —
30
+ pluggable `/readyz` database probe; without one the server falls back to the
31
+ built-in Prisma ping when Prisma is present, else reports `'skipped'`.
32
+
10
33
  ## [0.1.5]
11
34
 
12
35
  ### Removed