@nxgt/graphql-codegen-zod 0.2.1 → 0.2.2

package/README.md

@@ -34,7 +34,8 @@ Write the SDL files codegen reads: `@constraint` from
 `@nxgt/graphql-validation` and the custom scalars from `@nxgt/graphql-scalars`.
 Install both, so their bins are yours, whatever the package manager links:
 `bun add @nxgt/graphql-validation @nxgt/graphql-scalars` (the generated file
-imports `@nxgt/graphql-scalars` at run time anyway). Without the directive
+imports `@nxgt/graphql-scalars` at run time, unless it takes `@nxgt/zod`; see
+below). Without the directive
 nothing is constrained; plain types are still generated.
 
 ```sh
@@ -72,6 +73,10 @@ const config: CodegenConfig = {
 export default config;
 ```
 
+A client that only runs the generated file can set
+`scalarSchemas: '@nxgt/zod'` instead: the same record, without `graphql`. See
+[On a client](docs/guide/output.md#on-a-client-nxgtzod).
+
 The plugin writes types named as `@graphql-codegen/typescript` names them
 (`SignUpInput`, `MutationSignUpArgs`), which would collide with that plugin's
 in one file. Its `*Args` and `*Variables` types can replace the typescript

package/docs/guide/output.md

@@ -413,7 +413,7 @@ A custom scalar needs a Zod schema from you, mapped in one of two ways:
 
 | Option | Type | Effect |
 | --- | --- | --- |
-| `scalarSchemas` | `string` | a module exporting a `scalarSchemas` record keyed by GraphQL name; `@nxgt/graphql-scalars` exports one from 0.4.0 |
+| `scalarSchemas` | `string` | a module exporting a `scalarSchemas` record keyed by GraphQL name; `@nxgt/graphql-scalars` exports one from 0.4.0, `@nxgt/zod` from 0.1.0 |
 | `zodScalars` | `Record<string, string>` | `'<module>#<export>'` for one scalar; wins over the record |
 
 ```ts
@@ -435,6 +435,39 @@ birth: scalarSchemas.DateTime.nullish(),
 price: moneySchema,
 ```
 
+### On a client: `@nxgt/zod`
+
+`@nxgt/zod` exports the same `scalarSchemas` record, with the rules of
+`@nxgt/graphql-scalars`, and does not depend on `graphql`. A client that only
+runs the generated file imports it instead, and keeps `graphql` out of its
+bundle:
+
+```ts
+config: { scalarSchemas: '@nxgt/zod' },
+```
+
+```ts
+// what the generated file imports
+import { z } from "zod";
+import { scalarSchemas } from "@nxgt/zod";
+```
+
+The generated schemas are the same either way; only the import changes. The
+SDL codegen reads still comes from `@nxgt/graphql-scalars`
+(`bunx nxgt-graphql-scalars typedefs --out`), so a client installs it as a
+devDependency and `@nxgt/zod` as a dependency. Everything codegen needs is a
+devDependency too, so `graphql` never reaches the bundle: the generated file
+imports only `zod` and `@nxgt/zod`.
+
+```sh
+bun add @nxgt/zod zod
+bun add -d @nxgt/graphql-codegen-zod @nxgt/graphql-validation @nxgt/graphql-scalars
+bun add -d graphql @graphql-codegen/cli typescript
+```
+
+Under `moduleResolution` `nodenext` or `node16`, use `@nxgt/zod` 0.1.2 or
+later.
+
 - Two exports with the same name from different modules are aliased:
   `import { schema } from "./money"; import { schema as schema2 } from "./cost";`.
 - Module paths are written as they are in the generated file, so a relative

package/docs/roadmap.md

@@ -4,10 +4,7 @@ What `@nxgt/graphql-codegen-zod` is heading for, phrased as what you get.
 
 ## Now
 
-- **Output types.** Zod schemas and types for the SDL's object types,
-  interfaces and unions, and for each named operation's result and each
-  fragment, with `__typename` discriminating abstract types. Both parts are
-  written; they ship with the next release.
+Nothing in progress.
 
 ## Next
 
@@ -32,6 +29,13 @@ Nothing yet.
 
 ## Shipped
 
+- **Declarations that resolve under `nodenext`, 0.2.1.** The generated
+  file's `scalarSchemas` import typechecks with `moduleResolution`
+  `nodenext` or `node16`, with `@nxgt/graphql-scalars` 0.4.1 or later.
+- **Output types, 0.2.0.** Zod schemas and types for the SDL's object types,
+  interfaces and unions, and for each named operation's result and each
+  fragment, with `__typename` discriminating abstract types; `objects: false`
+  or `operations: false` turns either part off.
 - **The first release, 0.1.0.** Zod 4 schemas and types for enums, input
   types, field arguments and operation variables, carrying every
   `@constraint` of `@nxgt/graphql-validation`, so the client refuses what the

package/docs/troubleshooting.md

@@ -159,6 +159,18 @@ query Both($e: String, $u: String) { e(v: $e) u(v: $u) }
 bun add @nxgt/graphql-scalars@latest
 ```
 
+### `TS2305: Module '"@nxgt/zod"' has no exported member 'scalarSchemas'`
+
+**When:** type-checking the generated file under `moduleResolution`
+`nodenext` or `node16`, with `scalarSchemas: '@nxgt/zod'`.
+**Why:** `@nxgt/zod` before 0.1.2 ships declarations that `nodenext` does not
+resolve.
+**Fix:** upgrade it to 0.1.2 or later.
+
+```bash
+bun add @nxgt/zod@latest
+```
+
 ### `Property 'Money' does not exist on type '{ DateTime: ... }'` (or `TS2339`)
 
 **When:** type-checking the generated file, with `scalarSchemas` set.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@nxgt/graphql-codegen-zod",
-	"version": "0.2.1",
+	"version": "0.2.2",
 	"description": "A graphql-codegen plugin that writes Zod schemas from your SDL — inputs, enums, field arguments, operation variables, operation results and output types — with the @constraint rules of @nxgt/graphql-validation",
 	"license": "MIT",
 	"type": "module",
@@ -51,6 +51,7 @@
 	},
 	"devDependencies": {
 		"@nxgt/graphql-scalars": "^0.4.1",
+		"@nxgt/zod": "^0.1.2",
 		"@types/bun": "^1.4.0",
 		"graphql": "16.11.0",
 		"zod": "4.6.5"