@prisma-next/config - npm Package Compare versions

Comparing version

+8

-7

package.json

		{
		"name": "@prisma-next/config",
		"version": "0.14.0-dev.4",
		"version": "0.14.0-dev.5",
		"license": "Apache-2.0",
		@@ -9,10 +9,11 @@ "type": "module",
		"dependencies": {
		"@prisma-next/contract": "0.14.0-dev.4",
		"@prisma-next/framework-components": "0.14.0-dev.4",
		"@prisma-next/utils": "0.14.0-dev.4",
		"arktype": "^2.2.0"
		"@prisma-next/contract": "0.14.0-dev.5",
		"@prisma-next/framework-components": "0.14.0-dev.5",
		"@prisma-next/utils": "0.14.0-dev.5",
		"arktype": "^2.2.0",
		"pathe": "^2.0.3"
		},
		"devDependencies": {
		"@prisma-next/tsconfig": "0.14.0-dev.4",
		"@prisma-next/tsdown": "0.14.0-dev.4",
		"@prisma-next/tsconfig": "0.14.0-dev.5",
		"@prisma-next/tsdown": "0.14.0-dev.5",
		"tsdown": "0.22.1",
		@@ -19,0 +20,0 @@ "typescript": "5.9.3",

+3

-3

README.md

		@@ -28,3 +28,3 @@ # @prisma-next/config

		- Config file discovery/loading (`c12`, file I/O) - handled by `@prisma-next/cli`
		- Config file discovery/loading (`c12`, file I/O) - handled by `@prisma-next/config-loader`
		- CLI error envelope formatting and rendering - handled by CLI/errors package error utilities
		@@ -58,3 +58,3 @@ - Control-plane migration operations and runtime actions
		emitted artifact paths derived from `contract.output` (for example `contract.json` or the
		colocated `contract.d.ts`); the CLI loader resolves and validates those paths before emit/watch
		commands run. Tooling should always treat the config module graph as watched by default.
		colocated `contract.d.ts`); `@prisma-next/config-loader` resolves and validates those paths
		before emit/watch commands run. Tooling should always treat the config module graph as watched by default.

Improved metrics