arthurfiorette
An Important Update on Maintenance
To everyone who uses and supports this project, thank you. I'm incredibly proud that prisma-json-types-generator has become the most downloaded prisma community generator, with over 142,000 weekly downloads.
Because of this, I want to be transparent about the future of the project.
A generator's stability depends completely on Prisma itself. With Prisma's two week release schedule, breaking changes happen often. The only way to prepare for these changes is to have direct communication with the Prisma team.
I have been trying to work with the Prisma team since December 2024. I reached out through their private channels and suggested ways we could collaborate, like adding this generator to their own test suite ensuring no break changes happen or at least warn me beforehand so I can fix it in time.
This would help catch bugs before releases and reduce the gap between prisma releases and prisma-json-types-generator compatibility releases, making the experience better for everyone. Unfortunately, my messages and proposals have gone unanswered. Without collaboration, it has become impossible for me to guarantee the generator will work from one release to the next.
This situation means I have to change how I maintain the project. I will continue to accept PRs fixing bugs and adding support for future Prisma releases, but I can no longer proactively work on major feature requests like TypedSQL or queryCompiler support. These features would require deeper collaboration with the Prisma team, which is currently not available.
Unless this situation changes, the project will focus on stability rather than new features.
Thank you for your understanding.
This is my personal open source project and opinions expressed are my own, unrelated to my work/employer
This decision has been made after Prisma closed https://github.com/prisma/prisma/issues/27382 due to "inactivity", the same issue they redirected me to wait on in their private #collab-custom-generators channel.
To avoid burdening users, I'm removing the patch version constraint to allow any minor Prisma release to work with this package. However, since Prisma follows marketing releases rather than conventional semver (especially for internal packages that generators depend on), I cannot guarantee this will work seamlessly with future Prisma versions.
The Prisma maintainers need to do some self-reflection. Although they present themselves as open source and indeed are open source, they also provide paid services, which leads them to prioritize releases that are good for marketing. If they disregard the efforts of contributors like you who genuinely want to support the ecosystem, they undermine long-term and compounding growth. This is an ambiguous stance.
Not sure I follow, I see this as the last post and then there was no comment after that: https://github.com/prisma/prisma/issues/27382#issuecomment-3144649536
Not sure I follow, I see this as the last post and then there was no comment after that: prisma/prisma#27382 (comment)
What I also sent in their private channel (still unanswered):
I fixed that issue and released a patch 11 days after it was reported. The problem isn't that specific bug. What I've been trying to address is a broader collaboration. I've proposed a concrete solution to integrate some popular generators into your CI to prevent breaking changes or at least warn us about them when they happen, but I got redirected to wait on a individual bug report that just got closed. The community has expressed similar concerns about generator support being deprioritized. The DMMF is missing a lot of information that's declared in schemas, and there are many open issues about this with little to no progress. I'm fine fixing bugs when they come up, but I can't keep playing whack-a-mole with breaking changes when your team won't engage in basic collaboration to prevent them.
Yeah man, this really blows.
One one hand I'd say please maintain this since it makes Prisma somewhat usable. On the other hand, I'd say stop spending your time maintaining this. Prisma is taking your effort with zero care and profitting off of it. Don't let yourself get walked on like that. Just stop all updates to this project.
It's unfortunate, but hopefully acts as a wakeup call to all of us Prisma users to move to a better ORM
@arthurfiorette Hi, there is a new open source ORM library being rewritten from stretch https://zenstack.dev/v3 It supports Custom types as json field
@janpio Sad to see this, especially the communication piece; anything that can be done about this? This project became extremely vital in conjunction with using Prisma in our projects.
@sreuter I would love to, but I don't work at Prisma any more and so unfortunately can not help with this problem.
(In the past https://github.com/prisma/ecosystem-tests/tree/dev/community-generators/prisma-json-schema-generator would have been used to surface upcoming breakage and coordinate early remediations - not sure that is still a thing.)
Yeah, I remember being dm'ed multiple times to coordinate fixes so new releases wouldn't break anyone. Sadly, this doesn't seem to be a thing anymore.
Prisma decided to stay silent about this matter.
I'm not sure but is it possible that Prisma might be working to support this natively?
I hadn’t seen this before, but I share your frustration and anger. My team and I rack our brains trying not to update to any new version of Prisma, and instead stay on a fixed one, because otherwise VSCode stops working and things break.
Incredibly, the Prisma team has the audacity to reference this library in their documentation (prisma-json-types-generator), and yet it’s unacceptable that they don’t make sure nothing breaks when updating their stuff.
Thank you for your incredible job! Even though with the little that I have contributed to this library I am with you since Prisma does not even respond to what is pointed out in Twitter.
I don't work at Prisma any more
That’s two pieces of bad news in one issue :(
@arthurfiorette I'm not familiar with how you're testing the library against the latest prisma changes or exactly how prisma prepares branches before publishing a new version (I couldn't find a generic develop branch or anything of the sort).
That being said, I imagine that you could add a daily github action on this repo that checks prisma branches/commits etc. and kicks off a separate GH action for each branch/commit it deems worthy to test against (maybe a naming scheme regex or a recent commits check). Then the separate GH action can pull that branch/commit and run this repos tests against that version of prisma.
It isn't really as realtime or ideal as you're asking for, but it should at least give you a heads up when you see failures occurring that an upcoming release may have breaking changes...
(I couldn't find a generic develop branch or anything of the sort)
@Jackman3005 Each merge to main in prisma/prisma is shipped to npm as a -dev.x version on the dev dist tag. For the release every few weeks the latest from dev is republished as the new version, so testing against the dev version will surface things that could end up in the next release (but of course there might also be temporary expected breakage).
Reached out to Prisma's Discord about an issue I was having while upgrading to v7 (prisma-json-types-generator is on v6 and thus was causing issues).
Got someone from the Prisma staff to respond, hopefully we'll get a confirmation on what's next (if not, then they're clearly ignoring it).
After I opened this issue, a bunch of people reached out to me privately saying their projects rely on this package and asking me to keep it alive. And honestly, dropping it now would make me act exactly like Prisma did when they started ignoring this matter.
As of today, September 23rd, 2025, I still haven’t heard anything back from the message I posted in their internal channel on August 20th. I still have no idea why any of this even started. I’ve been ignored even when I asked about why I was being ignored lol
Anyway, I’ve kept merging the PRs you all send (And ended up removing the patch version constraint), and I’ll keep shipping updates whenever new PRs from you all come in...
Also, quick heads up: I just released beta support for Prisma v7! Please try it out and report any bugs (or a PR fixing them).
Happy to keep the open-source flame burning :)
If your company/project depends on this project, consider mentioning it to your boss and letting them know how important it is for your stack. I’d really appreciate any support through my GitHub Sponsors :)
After merging some almost copilot-only PRs, I've just released a stable 4.0.0 version supporting prisma v7.1+
Also dropping my GitHub Sponsors link here if you’d like to help me cover the AI bill that fixed almost all opened issues. 😅