@luckystack/core 0.5.0 → 0.5.1
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 +48 -48
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,48 +1,48 @@
|
|
|
1
|
-
# Changelog
|
|
2
|
-
|
|
3
|
-
All notable changes to `@luckystack/core` are documented in this file.
|
|
4
|
-
|
|
5
|
-
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
|
-
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
|
-
|
|
8
|
-
## [Unreleased]
|
|
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
|
-
|
|
33
|
-
## [0.1.5]
|
|
34
|
-
|
|
35
|
-
### Removed
|
|
36
|
-
|
|
37
|
-
- **`DNS` dropped from the env schema.** It was a reserved/legacy var that
|
|
38
|
-
conflated the backend origin (OAuth callback host) with the public origin
|
|
39
|
-
(where users browse). Projects now derive the backend origin from
|
|
40
|
-
`SERVER_IP`/`SERVER_PORT` and set the public origin via `app.publicUrl` (see the
|
|
41
|
-
scaffold's `config.ts`). Leftover `DNS=` lines in existing `.env` files are
|
|
42
|
-
harmless — the schema is `loose()`, so unknown keys pass through ignored.
|
|
43
|
-
|
|
44
|
-
## [0.1.0]
|
|
45
|
-
|
|
46
|
-
### Added
|
|
47
|
-
|
|
48
|
-
- Initial public release as part of the LuckyStack package split.
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to `@luckystack/core` are documented in this file.
|
|
4
|
+
|
|
5
|
+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
|
+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
|
+
|
|
8
|
+
## [Unreleased]
|
|
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
|
+
|
|
33
|
+
## [0.1.5]
|
|
34
|
+
|
|
35
|
+
### Removed
|
|
36
|
+
|
|
37
|
+
- **`DNS` dropped from the env schema.** It was a reserved/legacy var that
|
|
38
|
+
conflated the backend origin (OAuth callback host) with the public origin
|
|
39
|
+
(where users browse). Projects now derive the backend origin from
|
|
40
|
+
`SERVER_IP`/`SERVER_PORT` and set the public origin via `app.publicUrl` (see the
|
|
41
|
+
scaffold's `config.ts`). Leftover `DNS=` lines in existing `.env` files are
|
|
42
|
+
harmless — the schema is `loose()`, so unknown keys pass through ignored.
|
|
43
|
+
|
|
44
|
+
## [0.1.0]
|
|
45
|
+
|
|
46
|
+
### Added
|
|
47
|
+
|
|
48
|
+
- Initial public release as part of the LuckyStack package split.
|