"No Exported Member" Prisma Issues occurring after reinstalled dependencies w/SDK exit code 2
Hey, after running reinstalling dependencies I've had a number of issues suddenly come up, with several wasp warnings (all around prisma seemingly), and sdk build failing with exit code 2.
I've gone back and copied the exact package json used in the open saas template to make sure it's not an issue with a wrong dependency version but even with 1:1 replication it still fails
5 Replies
Hi @CamBlackwood. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry to hear you're experiencing issues with Prisma after reinstalling dependencies. Based on the knowledge sources provided, there are a few potential solutions you could try:
1. Check your Prisma version: There have been instances where Wasp failed to use the correct Prisma version, which was resolved by changing how Prisma was installed (source (https://github.com/wasp-lang/wasp/issues/631)). Also, there was an issue where Prisma introduced breaking changes in version 2.13, which was resolved by fixing the version of Prisma to 2.12 (source (https://github.com/wasp-lang/wasp/issues/158)). Make sure you're using a compatible version of Prisma.
2. Check for a
package.json above your Wasp project: There's an open issue where if there's a package.json above the Wasp project, the Prisma version from it will be used, which can cause issues (source (https://github.com/wasp-lang/wasp/issues/787)). If you have a package.json in a directory above your Wasp project, consider moving your project or the package.json.
3. Try running wasp clean and then wasp start again: This was suggested in a Discord support thread as a potential solution to a Prisma error (source (https://discord.com/channels/686873244791210014/1204021576979324949)).
4. Check your entities/index.ts file: There was a Discord support thread where a user received a "No Exported Member" error from Prisma in their entities/index.ts file (source (https://discord.com/channels/686873244791210014/1205259772828590110)). Make sure your entities/index.ts file is correctly exporting your Prisma models.
If none of these solutions work, it might be helpful to provide more specific error messages or details about your setup.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @CamBlackwood, 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?Thanks bot! suggestion 3 looks like it did the trick 🫡
@CamBlackwood glad you solved it!
Just for us to figure out what is the exact cause, and maybe avoid the need for
wasp clean in this situation in the future: what do you mean by "reinstalling dependencies"? What exactly did you do to get into this state where you needed wasp clean to get you out?I think I installed some conflicting version of typescript and then attempted to install deps manually outside of wasp, but I can't say for sure, sorry
Ok no worries, that makes sense!