@pothos/plugin-prisma with typescript as devDependency

[nephix]

Hi 👋

I'm using pothos and the @pothos/plugin-prisma plugin to generate types from prisma schema. This works well in development as typescript is listed under devDependencies:

"devDependencies": {
    "typescript": "^5.1.3",
    ...
  },
  "dependencies": {
    "@pothos/core": "^3.38.0",
    "@pothos/plugin-prisma": "^3.61.0",
    "@prisma/client": "^5.5.2",
    "prisma": "^5.5.2",
    ...
  },

but when building our backend docker image for production I run into an issue: I need to run

npx prisma generate

to generate the prisma client within node_modules.

But since we use the pothos prisma plugin, our schema.prisma includes:

generator pothos {
  provider     = "prisma-pothos-types"
  clientOutput = "@prisma/client"
  output       = "../src/generated/types.ts"
}

which requires typescript to be listed under dependencies instead of devDependencies (we omit installation of devDependencies via npm install --omit=dev)

I know that we can generate the prisma client into a different location so that it's part of the repository, but that seems to have it's own drawbacks.

Is there a way to skip the generation of the prisma-pothos-types provider depending on an env var like NODE_ENV? Or any better solutions?

Cheers

[nephix]

Ok it doesn't seem to be possible without saving the generated client outside of node_modules

[hayes]

This isn't currently a feature, but happy to accept a PR to add it

[nephix]

@hayes I'd be willing to do this, but I may need a couple of pointers into right direction. What's the best way to get in touch with you?

[hayes]

The discord channel (linked fr.the docs site) works well. I'm in the middle of moving right now, so my availability is a bit scattered

[nephix]

I don't really use Discord. Would you like me to create an issue for this instead

[hayes]

Yeah, GitHub issue is fine too!