W
Wasp7mo ago
JLegendz

Safe to do major prisma update?

My console informed me that there is a major Prima update available. Is it safe to update?
[ Db !] ┌─────────────────────────────────────────────────────────┐
[ Db !] │ Update available 4.16.2 -> 5.14.0 │
[ Db !] │ │
[ Db !] │ This is a major update - please follow the guide at │
[ Db !] │ https://pris.ly/d/major-version-upgrade │
[ Db !] │ │
[ Db !] │ Run the following to update │
[ Db !] │ npm i --save-dev prisma@latest │
[ Db !] │ npm i @prisma/client@latest │
[ Db !] └─────────────────────────────────────────────────────────┘
[ Db !] ┌─────────────────────────────────────────────────────────┐
[ Db !] │ Update available 4.16.2 -> 5.14.0 │
[ Db !] │ │
[ Db !] │ This is a major update - please follow the guide at │
[ Db !] │ https://pris.ly/d/major-version-upgrade │
[ Db !] │ │
[ Db !] │ Run the following to update │
[ Db !] │ npm i --save-dev prisma@latest │
[ Db !] │ npm i @prisma/client@latest │
[ Db !] └─────────────────────────────────────────────────────────┘
4 Replies
kapa.ai
kapa.ai7mo ago
Hi @JLegendz. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- While it's generally a good practice to keep your dependencies up-to-date, major updates can introduce breaking changes. Therefore, it's important to proceed with caution when updating Prisma to a major version. Here are some considerations based on the knowledge sources: 1. Check for breaking changes: Major updates often come with breaking changes. You should review the upgrade guide (https://pris.ly/d/major-version-upgrade) provided by Prisma to understand what changes are introduced in the new version and how they might affect your project. For example, when Wasp updated Prisma from v2 to v3, it was observed that the db migrate-dev command tried to recreate all migrations as new ones, ignoring the existing migrations [source (https://github.com/wasp-lang/wasp/issues/359)]. 2. Test thoroughly: After updating, you should thoroughly test your application to ensure everything still works as expected. In one instance, a version bump from Prisma 4.12 to 4.16 introduced a regression in Wasp's full-stack type safety DX [source (https://github.com/wasp-lang/wasp/issues/1570)]. 3. Consider the impact on Wasp: Wasp has its own dependencies and features that rely on Prisma. For example, Wasp uses Prisma middleware for certain operations, which was deprecated in favor of "client extensions" in Prisma 4.12 [source (https://github.com/wasp-lang/wasp/issues/1281)]. Therefore, you should also check if Wasp has any specific requirements or compatibility issues with the new Prisma version. In conclusion, while it's generally safe to update Prisma, you should do so carefully, taking into account the potential impact on your project and Wasp. Always follow the upgrade guide, test thoroughly, and consider Wasp's specific requirements and compatibility. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @JLegendz, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
miho
miho7mo ago
Prisma is a "Wasp owned dependency" and you can't update it yourself 🙂 We do have some good news that we are looking to upgrade to Prisma 5 soon. The Prisma version 4 works just fine until then no worries 🙂
JLegendz
JLegendzOP7mo ago
Sounds good!
martinsos
martinsos7mo ago
Yeah sorry about that, we added in new (unreleased yet) version of Wasp supression of that message, so it stops confusing people! And as Miho said, we will be doing the update for you soon.
Want results from more Discord servers?
Add your server