@prisma-next/cli 0.1.0-dev.10 → 0.1.0-dev.12
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/README.md +6 -6
- package/package.json +9 -9
package/README.md
CHANGED
|
@@ -53,7 +53,7 @@ The `contract emit` command requires a `driver` in the config (even though it do
|
|
|
53
53
|
import { defineConfig } from '@prisma-next/cli/config-types';
|
|
54
54
|
import postgresAdapter from '@prisma-next/adapter-postgres/control';
|
|
55
55
|
import postgresDriver from '@prisma-next/driver-postgres/control';
|
|
56
|
-
import postgres from '@prisma-next/
|
|
56
|
+
import postgres from '@prisma-next/target-postgres/control';
|
|
57
57
|
import sql from '@prisma-next/family-sql/control';
|
|
58
58
|
import { contract } from './prisma/contract';
|
|
59
59
|
|
|
@@ -134,7 +134,7 @@ The `db verify` command requires a `driver` in the config to connect to the data
|
|
|
134
134
|
import { defineConfig } from '@prisma-next/cli/config-types';
|
|
135
135
|
import postgresAdapter from '@prisma-next/adapter-postgres/control';
|
|
136
136
|
import postgresDriver from '@prisma-next/driver-postgres/control';
|
|
137
|
-
import postgres from '@prisma-next/
|
|
137
|
+
import postgres from '@prisma-next/target-postgres/control';
|
|
138
138
|
import sql from '@prisma-next/family-sql/control';
|
|
139
139
|
import { contract } from './prisma/contract';
|
|
140
140
|
|
|
@@ -287,7 +287,7 @@ The `db introspect` command requires a `driver` in the config to connect to the
|
|
|
287
287
|
import { defineConfig } from '@prisma-next/cli/config-types';
|
|
288
288
|
import postgresAdapter from '@prisma-next/adapter-postgres/control';
|
|
289
289
|
import postgresDriver from '@prisma-next/driver-postgres/control';
|
|
290
|
-
import postgres from '@prisma-next/
|
|
290
|
+
import postgres from '@prisma-next/target-postgres/control';
|
|
291
291
|
import sql from '@prisma-next/family-sql/control';
|
|
292
292
|
|
|
293
293
|
export default defineConfig({
|
|
@@ -438,7 +438,7 @@ The `db sign` command requires a `driver` in the config to connect to the databa
|
|
|
438
438
|
import { defineConfig } from '@prisma-next/cli/config-types';
|
|
439
439
|
import postgresAdapter from '@prisma-next/adapter-postgres/control';
|
|
440
440
|
import postgresDriver from '@prisma-next/driver-postgres/control';
|
|
441
|
-
import postgres from '@prisma-next/
|
|
441
|
+
import postgres from '@prisma-next/target-postgres/control';
|
|
442
442
|
import sql from '@prisma-next/family-sql/control';
|
|
443
443
|
import { contract } from './prisma/contract';
|
|
444
444
|
|
|
@@ -620,7 +620,7 @@ The CLI uses a config file to specify the target family, target, adapter, extens
|
|
|
620
620
|
```typescript
|
|
621
621
|
import { defineConfig } from '@prisma-next/cli/config-types';
|
|
622
622
|
import postgresAdapter from '@prisma-next/adapter-postgres/control';
|
|
623
|
-
import postgres from '@prisma-next/
|
|
623
|
+
import postgres from '@prisma-next/target-postgres/control';
|
|
624
624
|
import sql from '@prisma-next/family-sql/control';
|
|
625
625
|
import { contract } from './prisma/contract';
|
|
626
626
|
|
|
@@ -724,7 +724,7 @@ See `.cursor/rules/config-validation-and-normalization.mdc` for detailed pattern
|
|
|
724
724
|
|
|
725
725
|
### Pack Assembly
|
|
726
726
|
- **Family instances** now handle pack assembly internally. The CLI creates a family instance via `config.family.create()` and reads assembly data (operation registry, type imports, extension IDs) from the instance.
|
|
727
|
-
- **Removed**: `pack-assembly.ts` has been removed. Pack assembly is now handled by family instances. For SQL family, tests can import pack-based helpers directly from `packages/sql/family/src/core/assembly.ts` using relative paths.
|
|
727
|
+
- **Removed**: `pack-assembly.ts` has been removed. Pack assembly is now handled by family instances. For SQL family, tests can import pack-based helpers directly from `packages/2-sql/3-tooling/family/src/core/assembly.ts` using relative paths.
|
|
728
728
|
- Assembly logic is family-specific and owned by each family's instance implementation (e.g., `createSqlFamilyInstance` in `@prisma-next/family-sql`).
|
|
729
729
|
|
|
730
730
|
### Output Formatting (`utils/output.ts`)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@prisma-next/cli",
|
|
3
|
-
"version": "0.1.0-dev.
|
|
3
|
+
"version": "0.1.0-dev.12",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"sideEffects": false,
|
|
6
6
|
"files": [
|
|
@@ -19,9 +19,9 @@
|
|
|
19
19
|
"string-width": "^7.2.0",
|
|
20
20
|
"strip-ansi": "^7.1.2",
|
|
21
21
|
"wrap-ansi": "^9.0.2",
|
|
22
|
-
"@prisma-next/contract": "0.1.0-dev.
|
|
23
|
-
"@prisma-next/
|
|
24
|
-
"@prisma-next/
|
|
22
|
+
"@prisma-next/contract": "0.1.0-dev.12",
|
|
23
|
+
"@prisma-next/emitter": "0.1.0-dev.12",
|
|
24
|
+
"@prisma-next/core-control-plane": "0.1.0-dev.12"
|
|
25
25
|
},
|
|
26
26
|
"devDependencies": {
|
|
27
27
|
"@types/node": "^20.0.0",
|
|
@@ -29,11 +29,11 @@
|
|
|
29
29
|
"typescript": "^5.9.3",
|
|
30
30
|
"vite-tsconfig-paths": "^5.1.4",
|
|
31
31
|
"vitest": "^2.1.1",
|
|
32
|
-
"@prisma-next/sql-contract": "0.1.0-dev.
|
|
33
|
-
"@prisma-next/sql-contract-emitter": "0.1.0-dev.
|
|
34
|
-
"@prisma-next/sql-contract-ts": "0.1.0-dev.
|
|
35
|
-
"@prisma-next/sql-operations": "0.1.0-dev.
|
|
36
|
-
"@prisma-next/sql-runtime": "0.1.0-dev.
|
|
32
|
+
"@prisma-next/sql-contract": "0.1.0-dev.12",
|
|
33
|
+
"@prisma-next/sql-contract-emitter": "0.1.0-dev.12",
|
|
34
|
+
"@prisma-next/sql-contract-ts": "0.1.0-dev.12",
|
|
35
|
+
"@prisma-next/sql-operations": "0.1.0-dev.12",
|
|
36
|
+
"@prisma-next/sql-runtime": "0.1.0-dev.12",
|
|
37
37
|
"@prisma-next/test-utils": "0.0.1"
|
|
38
38
|
},
|
|
39
39
|
"exports": {
|