Troubleshooting

Common issues and their fixes.

Validation passes but types don't match (two TypeBox instances)

If Value.Check behaves oddly, or TypeScript complains that a generated schema isn't assignable to what your framework expects, you likely have two copies of TypeBox in your dependency tree: the generated files import from one, your app from another.

Set typeboxImportDependencyName to the same package your app imports TypeBox from. For example, if your app uses Elysia's re-export:

generator prismatype {
  provider = "prismatype"
  typeboxImportDependencyName = "elysia"
}

See Using the Schemas for the framework context.

My hand-written files in the output folder disappeared

PrismaType wipes and recreates the output directory on every prisma generate. Point output at a folder that PrismaType fully owns, and keep your own code elsewhere.

ERR_MODULE_NOT_FOUND / imports fail under nodenext

When your project uses "moduleResolution": "nodenext" (or otherwise requires explicit extensions), the extensionless imports between generated files won't resolve. Set importFileExtension to ".js":

generator prismatype {
  provider = "prismatype"
  importFileExtension = ".js"
}

Date values are rejected / serialize oddly

TypeBox 1.x has no Type.Date. PrismaType emits a refined Unsafe schema for DateTime by default. If you need JSON-serializable output, or want to accept native Date objects and transform them to strings, use useJsonTypes (true for formatted strings, "transformer" for a codec). See TypeBox & Nullability.

There's no separate schema for my MongoDB composite type

MongoDB composite types (type blocks) don't get their own exported schema. PrismaType inlines each composite type's Type.Object(...) directly into every model (and nested composite) that uses it, so a composite field appears inside the model's Plain schema rather than as an importable Address-style export. This is intentional; there is no separate file to import.

An annotation is being ignored

Each annotation must be on its own /// line; you cannot combine multiple annotations on one line. Also confirm the directive spelling against the Annotations reference. Any /// line that isn't a recognized annotation is treated as the field's description instead.

The generated __nullable__ / __transformDate__ names clash

Rename the helpers with nullableName and transformDateName. Prefix every exported schema with exportedTypePrefix if the model export names collide with other symbols in your app.