@prisma/composer 0.17.0-dev.3 → 0.17.0-dev.4
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@prisma/composer",
|
|
3
|
-
"version": "0.17.0-dev.
|
|
3
|
+
"version": "0.17.0-dev.4",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Prisma Composer — build a Prisma App by composing Modules. Core authoring, deploy pipeline, and the service-rpc/node/nextjs authoring surfaces. The `prisma-composer` CLI lives in @prisma/composer-cli.",
|
|
6
6
|
"exports": {
|
|
@@ -40,15 +40,15 @@
|
|
|
40
40
|
},
|
|
41
41
|
"devDependencies": {
|
|
42
42
|
"@effect/vitest": "4.0.0-rc.112",
|
|
43
|
-
"@internal/assemble": "0.17.0-dev.
|
|
44
|
-
"@internal/cli": "0.17.0-dev.
|
|
45
|
-
"@internal/core": "0.17.0-dev.
|
|
46
|
-
"@internal/foundation": "0.17.0-dev.
|
|
47
|
-
"@internal/lowering": "0.17.0-dev.
|
|
48
|
-
"@internal/nextjs": "0.17.0-dev.
|
|
49
|
-
"@internal/node": "0.17.0-dev.
|
|
50
|
-
"@internal/service-rpc": "0.17.0-dev.
|
|
51
|
-
"@internal/tsdown-config": "0.17.0-dev.
|
|
43
|
+
"@internal/assemble": "0.17.0-dev.4",
|
|
44
|
+
"@internal/cli": "0.17.0-dev.4",
|
|
45
|
+
"@internal/core": "0.17.0-dev.4",
|
|
46
|
+
"@internal/foundation": "0.17.0-dev.4",
|
|
47
|
+
"@internal/lowering": "0.17.0-dev.4",
|
|
48
|
+
"@internal/nextjs": "0.17.0-dev.4",
|
|
49
|
+
"@internal/node": "0.17.0-dev.4",
|
|
50
|
+
"@internal/service-rpc": "0.17.0-dev.4",
|
|
51
|
+
"@internal/tsdown-config": "0.17.0-dev.4",
|
|
52
52
|
"@types/node": "^26.0.1",
|
|
53
53
|
"tsdown": "^0.22.7",
|
|
54
54
|
"typescript": "^6.0.3"
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: prisma-composer-core-concepts
|
|
3
3
|
metadata:
|
|
4
4
|
library: "@prisma/composer"
|
|
5
|
-
library_version: "0.17.0-dev.
|
|
5
|
+
library_version: "0.17.0-dev.4"
|
|
6
6
|
version: 2026.9.1
|
|
7
7
|
description: >-
|
|
8
8
|
Use when deploying or managing an app that uses Prisma Composer
|
|
@@ -239,7 +239,7 @@ Two kinds of Postgres dependency:
|
|
|
239
239
|
`prisma contract emit`) is referenced by both the dependency end
|
|
240
240
|
(`deps: { db: postgres(catalogData) }`) and the resource end, which also
|
|
241
241
|
names the `prisma.config.ts` path so the deploy's migration step can
|
|
242
|
-
find `migrations/`.
|
|
242
|
+
reload the emitted `contract.json` and find `migrations/`.
|
|
243
243
|
|
|
244
244
|
**Deploys are replay-only**: they apply the migrations committed under
|
|
245
245
|
`migrations/` and never create schema themselves. Every schema change,
|
|
@@ -256,8 +256,12 @@ If no authored path reaches the target contract, deploy (and `dev` against a
|
|
|
256
256
|
stale local database) refuses with `MIGRATION_PATH_NOT_FOUND`; its message
|
|
257
257
|
lists the two ways out: author the missing migration, or, when iterating
|
|
258
258
|
against a local
|
|
259
|
-
database only, `prisma db update`.
|
|
260
|
-
|
|
259
|
+
database only, `prisma db update`. The tracked migration resource persists only
|
|
260
|
+
compact contract identity in deploy state; if the emitted contract artifact
|
|
261
|
+
named by `prisma.config.ts` is missing, unreadable, or no longer matches the
|
|
262
|
+
declared `dataContract(...)` value, deploy fails before touching the database.
|
|
263
|
+
Never skip step 3 before a deploy. See `examples/store/modules/catalog` for the
|
|
264
|
+
complete pattern.
|
|
261
265
|
|
|
262
266
|
## Deploy model: converge, don't script
|
|
263
267
|
|