@pikku/deploy 0.12.10 → 0.12.11
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 +26 -0
- package/dist/provider-adapter.d.ts +9 -9
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,31 @@
|
|
|
1
1
|
# @pikku/deploy
|
|
2
2
|
|
|
3
|
+
## 0.12.11
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- d10f5c2: Resolve a standalone build's database the way every other pikku host resolves it.
|
|
8
|
+
|
|
9
|
+
A standalone artifact opens its own database, and decided it had one by looking
|
|
10
|
+
for `db/sqlite` or `db/postgres` on disk. Every other host goes through
|
|
11
|
+
`loadUserConfigForDb`: `createConfig`'s `sqliteDb` / `postgresUrl` first, the
|
|
12
|
+
directory conventions only as the fallback. An app that declares its database in
|
|
13
|
+
config and keeps no migrations therefore got a `kysely` under `pikku dev` and
|
|
14
|
+
none in its artifact — a clean build, a plausible 94MB bundle, and a first run
|
|
15
|
+
that died on the line of `createSingletonServices` that reads it.
|
|
16
|
+
|
|
17
|
+
The build now asks the same question in the same order. Only the engine travels:
|
|
18
|
+
a configured SQLite path is a developer's local file and has no meaning on the
|
|
19
|
+
target host, which still names its own through `PIKKU_DATA_DIR`. Declaring both
|
|
20
|
+
dialects is refused by name, matching the existing refusal of two migration
|
|
21
|
+
directories, and a `createConfig` that cannot be loaded falls back to the
|
|
22
|
+
directories rather than failing a build — a project with no database at all must
|
|
23
|
+
still bundle.
|
|
24
|
+
|
|
25
|
+
Two JSDoc blocks that had drifted off their declarations are reattached:
|
|
26
|
+
`EntryGenerationContext['db']`, which was documenting `version`, and
|
|
27
|
+
`resolveStandaloneDb`, which was documenting `resolveProjectVersion`.
|
|
28
|
+
|
|
3
29
|
## 0.12.10
|
|
4
30
|
|
|
5
31
|
### Patch Changes
|
|
@@ -51,6 +51,15 @@ export interface EntryGenerationContext {
|
|
|
51
51
|
urlPrefix: string;
|
|
52
52
|
spaFallback: boolean;
|
|
53
53
|
};
|
|
54
|
+
/**
|
|
55
|
+
* The project's own version, for the artifact to report as its own.
|
|
56
|
+
*
|
|
57
|
+
* An operator holding a bundle on a machine has no other way to tell which
|
|
58
|
+
* build it is — there is no manifest to read and no registry to ask — and
|
|
59
|
+
* "which version is actually running" is the first question of every
|
|
60
|
+
* incident.
|
|
61
|
+
*/
|
|
62
|
+
version?: string;
|
|
54
63
|
/**
|
|
55
64
|
* The database the generated entry has to open for itself, or undefined when
|
|
56
65
|
* the project has none.
|
|
@@ -66,15 +75,6 @@ export interface EntryGenerationContext {
|
|
|
66
75
|
* business — a compiled bun binary and a node bundle do not open SQLite the
|
|
67
76
|
* same way, and Postgres is reached by URL rather than by path at all.
|
|
68
77
|
*/
|
|
69
|
-
/**
|
|
70
|
-
* The project's own version, for the artifact to report as its own.
|
|
71
|
-
*
|
|
72
|
-
* An operator holding a bundle on a machine has no other way to tell which
|
|
73
|
-
* build it is — there is no manifest to read and no registry to ask — and
|
|
74
|
-
* "which version is actually running" is the first question of every
|
|
75
|
-
* incident.
|
|
76
|
-
*/
|
|
77
|
-
version?: string;
|
|
78
78
|
db?: {
|
|
79
79
|
engine: 'sqlite' | 'postgres';
|
|
80
80
|
/**
|