This understandably caused a lot of frustration among a lot of you and we want to sincerely apologize for that! Note that during the rewrite we'll try to merge PRs from the community on a best effort basis that helps keep the plugin in sync with Prisma releases. We are very aware that the decision to rewrite the plugin and temporarily remove support for it came very suddenly and without prior notice. I also would like to add a few things to Spiros' ( initial message above! The path to migrate CRUD operations from t.crud() will be added very soon, sorry for the delay! 🙏 We just published the first half of the migration guide covering the migration from t.model() to vanilla Nexus here. It's just that the business side of me needs to make practical decisions the developer side of me wish you all a great rewrite & success story! Of course, I'm very appreciative of the open source community and developers working hard to improve this project, which I understand can mean making tough decisions like this. While I don't mean to be negative or ungrateful, we've just spent weeks migrating over from Nexus Framework after the migration guide for it specifically mentioned "Nexus Schema Prisma plugin is not being shut down." A stop of all bugfixes and being pegged to an old package is certainly cause for concern. Every migration as a package gets deprecated is expensive, and often we make these calls expecting that the migration will be the last one for a while. All these transitions and migrations have serious capital and productivity costs. My guess is that our needs are a bit different from folks just building smaller projects or using these frameworks as gateways to experiment with GraphQL. Side note - Are there other companies using Prisma and/or Nexus in production settings? If so, I would love to reach out to you and create a "support group" of sorts as we work through what this all means, and what good paths forward remain. Let us know if you have any questions by posting a comment in this issue, we're always happy to help! 💚 We apologize for the inconvenience and the delay in resolving your issues! Hopefully the improvements we introduce will make your wait worthwhile.
We also plan to write a migration guide for this and we'll let you know in the coming weeks about it. on Slack) if you have any questions about removing the the nexus-plugin-prisma from your application. If you want to use the newer Prisma versions, you can remove the Prisma plugin and still enjoy the Prisma benefits with Nexus. No new releases of the plugin to keep it up to date with new Prisma Client versions will be made, so the latest supported Client version is 2.14.0.We will not be able to fix any issues for the current versions of the plugin.
The unfortunate news are that in order to focus all of our efforts in the new version of the plugin, we will need to limit our time in maintaining the current versions, so we will have to temporarily drop support for the current versions of the plugin, which means that: This will allow us to properly maintain and support this new plugin surface in the long term and it will enable you to solve many of the issues you face like iterating over a large number of models or creating custom middleware. The vision we came up with is a lighter plugin which will replace the current API (like t.modeland the experimental t.crud) with a set of more programmatic capabilities for you to iterate over your Prisma Schema and create functionality like the existing and more. The new Nexus Prisma PluginĬonsidering the current state of the codebase and the varying types of issues, it is clear to us that we need to take a step back and, with all the accumulated knowledge so far, rethink how we want this to work. This makes it difficult for us to maintain, and even more difficult to bring new features to the plugin at the moment. The initial version of the codebase was created in a short period of time and has accumulated a lot of technical debt since then.
NEXUS PLUGIN SPECS UPDATE
In this GitHub issue, we want to provide an update on the current state of the plugin and give you a taste of what is coming next. It has not been a secret that maintenance work of the nexus-prisma-plugin has lagged behind the past few months. 👉 Go to the new Prisma plugin for Nexus:
0 kommentar(er)
