HI there! Currently debugging some crazy stuff with generating a prisma client with a custom output path into a monorepo man that's a lot of buzzwords I have found several open issues (and some old closed ones) with people who seem to have the same problem, wondering if this bug isn't a priority and I should just switch everything off of prisma? Issues are here: Technically Closed: https://github.com/prisma/prisma/issues/10512, Open: https://github.com/prisma/prisma/issues/13233, https://github.com/prisma/prisma/issues/12588, https://github.com/prisma/prisma/issues/10433 (my exact issue) I have figured out how to fix this sort of! I just had to manually edit the generated index.js file 😂 Details in the thread Hoping to get a real fix for this ❤️

Hey there Rox 👋 thanks for sharing your workaround! I’m sharing this internally and also added the info you shared to the issue so that others can find the workaround easier when they’re running into it as well🙏

thanks @nikolasburk I figured this out at 1am so I was dying and didn't wanna go to github yet lmao is there a fix that can be made to the generator that applies this workaround? I'm not deep enough in the prisma architecture to know