"Failed to parse static properties from plugin xxx" after installing @prisma/nuxt
Hello there. Im not entirely sure if i should complain to Prismas authors or here, but as pretty much everything breaks related to Nuxt, ill do it here.
Ever since i installed the @prisma/nuxt module using nuxi, everything likes to break at random. Right after i installed it i had to reinstall all my deps because of the errors in the attached image, but
npm run dev worked fine after that. When trying to build using npm run build, it also broke and as a result i got these errors. It seems like every module that ive installed is breaking - Pinia, Nuxt Icon, i18n, everything. Tried clearing the cache using npx nuxi cleanup and that didnt help a single bit. Anyone have a clue ?
5 Replies
Hi @Lean. 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 plugin parsing in Nuxt after installing the @prisma/nuxt module. This seems to be a known issue that has been reported by other users as well. Let me provide some insights and potential solutions based on the available information.
The error message "Failed to parse static properties from plugin xxx" is similar to an issue reported in Github Issue #30304. This issue seems to be related to compatibility problems between certain dependencies and recent versions of Nuxt.
Here are some steps you can try to resolve the issue:
1. Update your dependencies: Make sure all your Nuxt-related packages are up to date. You can try running
npm update or yarn upgrade depending on your package manager.
2. Check Vite version: As mentioned in one of the comments in the Github issue, the problem might be related to Vite v6. You can try installing a specific version of Vite that is known to work:
3. Disable devtools: If the issue persists, you can try disabling the Nuxt devtools in your nuxt.config.ts file:
4. Clear cache and reinstall dependencies: Although you mentioned that clearing the cache didn't help, it's worth trying again in combination with removing the node_modules folder and reinstalling dependencies:
5. Check for conflicting plugins: Review your installed plugins and modules to ensure there are no conflicts between them and the newly installed @prisma/nuxt module.
If none of these steps resolve the issue, it might be worth creating a minimal reproduction of the problem and reporting it to the Nuxt GitHub repository. You can follow the guidelines for reporting bugs to ensure you provide all the necessary information for the Nuxt team to investigate.
Remember that Nuxt is actively developed, and issues like this can sometimes occur with new updates or module installations. If you continue to face difficulties, you might want to consider reaching out to the Nuxt community through GitHub Discussions for more specific help tailored to your project setup.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@401116245857927199> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
1. tried, didnt fix
2. isnt that going to break nuxt even more?
3. no clue how this might help
4. just tried and results in the same
Theres also this
yeah its something to do with the @prisma/nuxt module, removed it, installed regular prisma and now it both runs fine and also builds fine. Just wanted to go the module route because it felt more integrated and stuff