some paths from `tsconfig.json > compilerOptions > paths` does not work on github actions for some reason

[touhidurrr]

Code

https://github.com/touhidurrr/uncivgames-dbot/blob/4114b95fd16bc3f3d43dc914fe02bb7314cee613/tsconfig.json#L25

Error

https://github.com/touhidurrr/uncivgames-dbot/actions/runs/24318899303/job/71001359980

[dario-piotrowicz]

Hi @touhidurrr, I don't see a generated directory in the prisma directory, so wrangler being unable to resolve it makes sense to me.

Am I missing something?

[touhidurrr]

Hi @touhidurrr, I don't see a generated directory in the prisma directory, so wrangler being unable to resolve it makes sense to me.

Am I missing something?

Yes. that directory is in gitignore. And typegen is supposed to regenerate it.

[edmundhung]

Hi @touhidurrr, this looks like a Prisma client setup issue rather than a Wrangler tsconfig.paths issue.

@prismaGenerated/edge maps to ./prisma/generated/edge, but Prisma 7's prisma-client generator does not appear to generate an edge entrypoint. That may have been confused with the older @prisma/client/edge import style.

Please compare your setup with Prisma's Cloudflare Workers guide:
https://www.prisma.io/docs/guides/deployment/cloudflare-workers

In particular, you likely need to set the Prisma generator runtime to cloudflare and import from the actual generated client entrypoint, typically @prismaGenerated/client rather than @prismaGenerated/edge.

If prisma/generated/edge is not present after prisma generate, Wrangler cannot resolve @prismaGenerated/edge.

[touhidurrr]

This is definitely a bug. Works locally but not in ci.

[touhidurrr]

Ok, not sure why it was working from local environment before. But making the following changes worked:

 generator client {
   provider = "prisma-client"
+  runtime  = "cloudflare"
   output   = "generated"
 }

-import { PrismaClient } from '@prismaGenerated/edge';
+import { PrismaClient } from '@prismaGenerated/client';

Thanks for the suggestion!