prisma 8.0.0-rc.19-dev.136 → 8.0.0-rc.20-dev.139
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/dist/prisma.js
CHANGED
|
@@ -1220,7 +1220,10 @@ async function readPastedCallbackUrl(rl, options) {
|
|
|
1220
1220
|
try {
|
|
1221
1221
|
answer = await rl.question("Paste the callback URL here: ", { signal: options.signal });
|
|
1222
1222
|
} catch (error) {
|
|
1223
|
-
if (error?.name === "AbortError")
|
|
1223
|
+
if (error?.name === "AbortError") {
|
|
1224
|
+
if (options.signal.aborted) return null;
|
|
1225
|
+
throw new CliStructuredError("CLI.PROMPT_CANCELLED", "Sign-in was cancelled before it completed.");
|
|
1226
|
+
}
|
|
1224
1227
|
throw error;
|
|
1225
1228
|
}
|
|
1226
1229
|
const trimmed = answer.trim().replace(/^["']|["']$/g, "");
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "prisma",
|
|
3
|
-
"version": "8.0.0-rc.
|
|
3
|
+
"version": "8.0.0-rc.20-dev.139",
|
|
4
4
|
"description": "The Prisma CLI: one binary for the ORM, Composer, and the Prisma Developer Platform.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -45,10 +45,10 @@
|
|
|
45
45
|
"dependencies": {
|
|
46
46
|
"@manypkg/tools": "^2.1.2",
|
|
47
47
|
"@prisma/cli-engine": "0.6.2",
|
|
48
|
-
"@prisma/composer-cli": "0.
|
|
48
|
+
"@prisma/composer-cli": "0.26.0-dev.2",
|
|
49
49
|
"@prisma/compute-sdk": "0.43.0",
|
|
50
50
|
"@prisma/management-api-sdk": "1.80.0",
|
|
51
|
-
"@prisma/orm-toolchain": "8.0.0-rc.
|
|
51
|
+
"@prisma/orm-toolchain": "8.0.0-rc.14-dev.24",
|
|
52
52
|
"@vercel/detect-agent": "^1.2.3",
|
|
53
53
|
"better-result": "^2.9.2",
|
|
54
54
|
"cross-spawn": "^7.0.6",
|
|
@@ -57,10 +57,10 @@
|
|
|
57
57
|
"open": "^11.0.0"
|
|
58
58
|
},
|
|
59
59
|
"devDependencies": {
|
|
60
|
-
"@prisma/cli": "8.0.0-rc.
|
|
60
|
+
"@prisma/cli": "8.0.0-rc.20-dev.139",
|
|
61
61
|
"@prisma/credentials-store": "^7.8.0",
|
|
62
|
-
"@repo/cli-telemetry": "8.0.0-rc.
|
|
63
|
-
"@repo/tsconfig": "8.0.0-rc.
|
|
62
|
+
"@repo/cli-telemetry": "8.0.0-rc.20-dev.139",
|
|
63
|
+
"@repo/tsconfig": "8.0.0-rc.20-dev.139",
|
|
64
64
|
"@types/node": "^22.19.19",
|
|
65
65
|
"tsdown": "^0.21.10",
|
|
66
66
|
"typescript": "^6.0.3",
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: prisma-platform-core-concepts
|
|
3
3
|
metadata:
|
|
4
4
|
library: "prisma"
|
|
5
|
-
library_version: "8.0.0-rc.
|
|
5
|
+
library_version: "8.0.0-rc.20-dev.139"
|
|
6
6
|
version: 2026.9.2
|
|
7
7
|
description: >-
|
|
8
8
|
Use when hosting, deploying, or operating an app on the Prisma Platform:
|
|
@@ -71,26 +71,42 @@ packages (`prisma-composer-core-concepts` in `@prisma/composer`,
|
|
|
71
71
|
`prisma-orm-core-concepts` in `@prisma/orm-postgres`), so they appear after
|
|
72
72
|
this install plus `prisma skills sync`, not before.
|
|
73
73
|
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
74
|
+
One config file, `prisma.config.ts`, configures the CLI and every product
|
|
75
|
+
it runs. Each top-level key is a section owned by one product, and this CLI
|
|
76
|
+
recognises exactly three: `orm`, `composer`, and `skills`. The composed
|
|
77
|
+
shape:
|
|
78
|
+
|
|
79
|
+
```ts
|
|
80
|
+
import { definePrismaConfig } from "prisma/config";
|
|
81
|
+
import { defineConfig as composer } from "@prisma/composer/config";
|
|
82
|
+
import { nodeBuild } from "@prisma/composer/node/control";
|
|
83
|
+
import {
|
|
84
|
+
prismaCloud,
|
|
85
|
+
prismaState,
|
|
86
|
+
} from "@prisma/composer-prisma-cloud/control";
|
|
87
|
+
import { defineConfig as orm } from "@prisma/orm-postgres/config";
|
|
88
|
+
|
|
89
|
+
export default definePrismaConfig({
|
|
90
|
+
composer: composer({
|
|
91
|
+
extensions: [prismaCloud(), nodeBuild()],
|
|
92
|
+
state: prismaState(),
|
|
93
|
+
}),
|
|
94
|
+
orm: orm({ contract: "./src/prisma/contract.prisma" }),
|
|
95
|
+
skills: { agents: ["claude"] },
|
|
96
|
+
});
|
|
97
|
+
```
|
|
89
98
|
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
99
|
+
`dev` and `deploy` read the `composer` section and nothing else; what goes
|
|
100
|
+
in it belongs to `prisma-composer-core-concepts`. A separate
|
|
101
|
+
`prisma-composer.config.ts` is no longer read, and the old setup is refused,
|
|
102
|
+
never silently ignored: `CONFIG.SECTION_MISSING` when no loaded
|
|
103
|
+
`prisma.config.ts` declares a `composer` section, `CONFIG.FIELD_RETIRED`
|
|
104
|
+
when the section still has `configPath`, and `CONFIG.FILE_RETIRED` when a
|
|
105
|
+
`prisma-composer.config.*` sits next to the declaring `prisma.config.ts`.
|
|
106
|
+
All three arrive under the CLI's `CLI.CONFIG_SECTION_INVALID`. For
|
|
107
|
+
`CONFIG.SECTION_MISSING`, write the section. For the other two, move the
|
|
108
|
+
old file's `extensions` and `state` into the section, then delete the
|
|
109
|
+
`configPath` field or the old file.
|
|
94
110
|
|
|
95
111
|
## The resource model
|
|
96
112
|
|