Is React Native Prisma Still Actively Maintained? Seeking Updates on Development & Future Plans

[sabaturgay]

First off, I want to sincerely appreciate the effort that has gone into building and maintaining this package. React Native Prisma has the potential to be a game-changer for local-first React Native apps, and I truly value its utility.

That said, I originally shared this issue on the React Native Prisma repo, but it seems like it hasn’t received much attention, so I wanted to bring it up here for better visibility.

I’ve noticed that updates to the repository have been infrequent, mostly focused on minor chores or small fixes. Given this, I wanted to check if the package is still actively maintained and whether there are plans for further development.

Specifically:

• There are unresolved blockers, such as issues when upgrading from Expo SDK 51 to 52, which prevent successful EAS builds.
• I previously submitted a pull request to fix a base64 utils issue, but it hasn’t seen much progress.
• Prisma has introduced new features like SQLite JSON support, which would be valuable additions to this package.

It would be great to get some clarity on the long-term roadmap and whether there’s an opportunity for contributors to help push forward key fixes and enhancements. Looking forward to any updates from the maintainers. Thanks again for your work! 🚀

[aqrln]

Thank you for your thoughtful message and for your interest in React Native Prisma. We truly appreciate the enthusiasm and contributions from the community. I have left a comment in your pull request, let's get it merged.

At the moment, our primary focus has been on other areas of the Prisma ecosystem, which means development on React Native Prisma hasn’t progressed as actively as some might hope. That said, we recognize its potential and the value it brings to certain workflows. While we don’t have any specific updates to share right now, I agree we should at least fix the current blockers and update it to be compatible with the latest version of the ORM.

Unfortunately, it looks like the issues and PRs in that repo have fallen through the cracks. We are improving our issue intake and triage processes to prevent problems like these going forward.

As for this issue specifically, I'm going to convert it to a discussion. Thank you again!