Update zod to v4 and patch compatibility

[DexterStorey]

Update zod-prisma-types to be compatible with Zod v4 by adjusting generator config parsing for new .default() semantics.

Zod v4 changed the behavior of .default(), causing it to short-circuit before transformations. This required reordering the transform and default calls for boolean string flags in the generator config schema to ensure correct parsing and default application.

---

Slack Thread

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[DexterStorey]

@cursor the zod/v4 needs to be imported with zod/v4, not just zod

[cursor]

I updated the import paths for the zod library across the generator's codebase and usage tests. This change specifically targets zod/v4 to ensure compatibility and prepare for future Zod versions.

• I modified the zod import statement from import { z } from 'zod'; to import { z } from 'zod/v4'; in the following core files:
  • packages/generator/src/classes/extendedDMMFInputType.ts
  • packages/generator/src/classes/extendedDMMFSchemaField.ts
  • packages/generator/src/generatorHandler.ts
  • packages/generator/src/schemas/generatorConfigSchema.ts
  • packages/generator/src/utils/getPrismaDbProvider.ts
  • packages/generator/src/utils/getPrismaVersion.ts
  • packages/generator/src/utils/skipGenerator.ts
  • packages/generator/src/functions/writeSingleFileImportStatements.ts
• I applied the same zod/v4 import path change across all relevant content writer functions within packages/generator/src/functions/contentWriters/, including writeArgs.ts, writeCountArgs.ts, writeModelOrType.ts, writeSelect.ts, and others, to ensure consistency in generated code.
• I updated the zod import in packages/usage/tests/implementations/decimalSchema.ts to zod/v4 to align the test suite with the new import strategy.

---

_{Learn more about Cursor Agents}