use a default import so that the code is ESM compatible

[capaj]

In one of the files generated I have:

import { Gender } from "@prisma/client"

export const _UserModel = z.object({
  id: z.string(),
  gender: z.nativeEnum(Gender),
})

this causes a problem when I use native ESM modules. Node.js is not able to import that as named export:

SyntaxError: Named export 'Gender' not found. The requested module '@prisma/client' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@prisma/client';
const { QuestionnaireScheduleType } = pkg;

it would be much better to generate the file like this:

import prisma from "@prisma/client"

export const _UserModel = z.object({
  id: z.string(),
  gender: z.nativeEnum(prisma.Gender),
})

this way it will work fine on commonJS and native ESM.

There is an issue in prisma repo which might explain the problem further:
prisma/prisma#4816

[CarterGrimmeisen]

Is this with "type": "module" or one of the command line flags for node?

[capaj]

I am using "type": "module"

[CarterGrimmeisen]

Okay, last question. I'm looking to try and test some of these changes myself. How are you running node on these typescript files? Are you just compiling them with tsc and then running them? Are you using ts-node? Thanks in advance for your help!

[capaj]

I am using ts-node like this:

https://twitter.com/capajj/status/1496057264586768388?t=h2WClBTeWWGEW5m-X6ZKkw&s=19

😅

[CarterGrimmeisen]

Could you test the fix from the fix/99 branch by placing this tarball (zod-prisma-v0.5.5.tar.gz) in your project directory and updating your package.json with the following?

"zod-prisma": "file:./zod-prisma-v0.5.5.tar.gz"

Thanks for your help!

[CarterGrimmeisen]

Whoops! You'll also have to add the following to your schema.prisma

generator zod {
  ...
  nodeEsModules = true // this line
}