prisma 8.0.0-rc.27-dev.167 → 8.0.0-rc.27-dev.169
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",
|
|
3
|
-
"version": "8.0.0-rc.27-dev.
|
|
3
|
+
"version": "8.0.0-rc.27-dev.169",
|
|
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,7 +45,7 @@
|
|
|
45
45
|
"dependencies": {
|
|
46
46
|
"@manypkg/tools": "^2.1.2",
|
|
47
47
|
"@prisma/cli-engine": "0.9.0",
|
|
48
|
-
"@prisma/composer-cli": "0.34.0-dev.
|
|
48
|
+
"@prisma/composer-cli": "0.34.0-dev.4",
|
|
49
49
|
"@prisma/compute-sdk": "0.43.0",
|
|
50
50
|
"@prisma/management-api-sdk": "1.80.0",
|
|
51
51
|
"@prisma/orm-toolchain": "8.0.0-rc.20-dev.11",
|
|
@@ -57,10 +57,10 @@
|
|
|
57
57
|
"open": "^11.0.0"
|
|
58
58
|
},
|
|
59
59
|
"devDependencies": {
|
|
60
|
-
"@prisma/cli": "8.0.0-rc.27-dev.
|
|
60
|
+
"@prisma/cli": "8.0.0-rc.27-dev.169",
|
|
61
61
|
"@prisma/credentials-store": "^7.8.0",
|
|
62
|
-
"@repo/cli-telemetry": "8.0.0-rc.27-dev.
|
|
63
|
-
"@repo/tsconfig": "8.0.0-rc.27-dev.
|
|
62
|
+
"@repo/cli-telemetry": "8.0.0-rc.27-dev.169",
|
|
63
|
+
"@repo/tsconfig": "8.0.0-rc.27-dev.169",
|
|
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.27-dev.
|
|
5
|
+
library_version: "8.0.0-rc.27-dev.169"
|
|
6
6
|
version: 2026.9.2
|
|
7
7
|
description: >-
|
|
8
8
|
Use when hosting, deploying, or operating an app on the Prisma Platform:
|
|
@@ -58,8 +58,13 @@ step and no connection strings to wire by hand; Composer injects them.
|
|
|
58
58
|
|
|
59
59
|
## Project setup
|
|
60
60
|
|
|
61
|
-
|
|
62
|
-
|
|
61
|
+
`prisma init` prepares local configuration and copies this skill from the
|
|
62
|
+
installed `prisma` package into the configured agent directories. Database
|
|
63
|
+
provisioning and deployment are separate choices. Keep the project's existing
|
|
64
|
+
database and hosting setup unless the user wants to change it.
|
|
65
|
+
|
|
66
|
+
For a Prisma Composer (Early Access) app deployed to Prisma Compute, install
|
|
67
|
+
the app's dependencies:
|
|
63
68
|
|
|
64
69
|
```sh
|
|
65
70
|
npm install prisma @prisma/composer @prisma/composer-prisma-cloud
|
|
@@ -211,6 +216,13 @@ runs. The first deploy creates the project, named after your module; the
|
|
|
211
216
|
name must be unique in the workspace, and `--name` deploys under a different
|
|
212
217
|
one.
|
|
213
218
|
|
|
219
|
+
Before deploying, configure the Composer root module and the `composer`
|
|
220
|
+
section in `prisma.config.ts`, then build the app. A new project also needs
|
|
221
|
+
a region in `prismaCloud({ region: ... })` or `PRISMA_REGION`. The
|
|
222
|
+
[deployment guide](https://www.prisma.io/docs/composer/deploying) covers
|
|
223
|
+
these prerequisites; running `prisma init` alone does not prepare a
|
|
224
|
+
deployable app.
|
|
225
|
+
|
|
214
226
|
Both paths converge the same declaration, so they are mutually idempotent:
|
|
215
227
|
a repo can be connected to GitHub and still be deployed from the CLI.
|
|
216
228
|
|
|
@@ -280,6 +292,15 @@ it. On paid plans, backups are automated, listable, and restorable.
|
|
|
280
292
|
Per-database usage metrics are queryable; the `postgres` group covers all of
|
|
281
293
|
it.
|
|
282
294
|
|
|
295
|
+
A database outside any project comes from the separate
|
|
296
|
+
[`create-db` tool](https://www.prisma.io/docs/postgres/npx-create-db):
|
|
297
|
+
`npx create-db@latest` needs no account and prints a connection string and a
|
|
298
|
+
claim URL. The database is deleted after 24 hours unless claimed; claiming it
|
|
299
|
+
with a Prisma account keeps it for free. Use it when the user has no Prisma
|
|
300
|
+
account or project yet. When the project is on the platform, create the
|
|
301
|
+
database in the project with the `postgres` group, or declare it in the
|
|
302
|
+
module, instead.
|
|
303
|
+
|
|
283
304
|
## Object storage
|
|
284
305
|
|
|
285
306
|
Buckets are S3-compatible object stores that live inside the project,
|