Prisma: has no exported member
I am trying to install the opensaas template with wasp 0.15.2 but getting this:
I read that 0.15 came with breaking changes, but i also read that the opensaas template is fit for 0.15.
7 Replies
Hi @InsOp. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, it appears that you're experiencing an issue related to Prisma client generation and compatibility. This problem is similar to what other users have reported when using Wasp with certain versions of Prisma. Here's what we can gather from the available information:
1. The error you're seeing is related to Prisma types not being properly exported or recognized. This could be due to a mismatch between the Prisma version used in the OpenSaaS template and the one Wasp is expecting.
2. A similar issue was reported in a Discord support thread, where a user encountered Prisma-related errors when trying to install the OpenSaaS template.
3. The recommended solution in that case was to try running
wasp clean
followed by wasp start
again. This seemed to resolve the issue for that user.
Given this information, here are some steps you can try:
1. First, run wasp clean
to remove any generated files that might be causing conflicts.
2. Then, run wasp start
again to regenerate the necessary files.
If the problem persists after trying these steps, it's possible that there might be a compatibility issue between the OpenSaaS template and Wasp 0.15.2. In this case, you might want to:
1. Check if there's an updated version of the OpenSaaS template specifically compatible with Wasp 0.15.2.
2. Report this issue on the Wasp GitHub repository or Discord channel, as it might be a bug that the Wasp team needs to address.
It's worth noting that Wasp is actively working on improving its integration with Prisma, as mentioned in a GitHub issue about migrating to the latest Prisma version. This suggests that such issues might be resolved in future updates.
If these steps don't resolve your issue, I recommend reaching out to the Wasp community on Discord or GitHub for more specific assistance, as they might have encountered and solved similar problems with the latest versions.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @InsOp, 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?btw this came when trying to execute
wasp db migrate-dev
I tried wasp clean alreadyalso i see this:
I fixed the version in the package.json for
"@prisma/client": "5.19.1",
(it was "@prisma/client": "^5.19.1",
before, this resulted in errors
now it worksi would create a PR but i dont find that module in the package.json here https://github.com/wasp-lang/open-saas/blob/main/template/app/package.json
GitHub
open-saas/template/app/package.json at main · wasp-lang/open-saas
A free, open-source SaaS app starter for React & Node.js with superpowers. Full-featured. Community-driven. - wasp-lang/open-saas
Wohooo @InsOp, you just became a Waspeteer level 1!
Could give us a bit more details for this bit:
I fixed the version in the package.json for "@prisma/client": "5.19.1", (it was "@prisma/client": "^5.19.1", before, this resulted in errorsWhere did you fix this version, in your project's
package.json
? How did the @prisma/client
end up there, did you run Prisma commands with npx prisma
maybe?