pinia: Pinia nuxt version 0.6.0+ causes error when used with pnpm monorepo
Reproduction
https://stackblitz.com/~/github.com/kalvenschraut/pinia-nuxt-pnpm-monorepo-issue
Steps to reproduce the bug
To see issue do
pnpm install
pnpm --filter website1 run dev
can then downgrade @pinia/nuxt to 0.5.5 and run same commands to see it working. Can also upgrade to 0.6.1 to verify still not working
pnpm update @pinia/nuxt@0.5.5 -r
pnpm --filter website1 run dev
Expected behavior
Page to load and show the users name from the user store
Actual behavior
Additional information
In prod builds on my personal site where I first initial saw this was seeing vueDemi.effectScope is not a function error. Downgrading back to 0.5.5 for now until direction can be given
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 15
- Comments: 30 (14 by maintainers)
Commits related to this issue
- fix: dedupe pinia Fix #2820 — committed to vuejs/pinia by posva 2 years ago
- fix: allow module to install pinia alongside This should allow the nuxt module to install pinia if needed Fix #2820 — committed to vuejs/pinia by posva 2 years ago
I’ve updated @nuxt/pinia to 0.7.0 last week and started running into this issue. Downgrading to 0.6.1 makes everything work again.
Additional data points:
EDIT: So 0.6.1 works in development (at least for me), but after a deploy to staging “everything” was broken. Only after downgrading to 0.5.5 did a deployed build work again.
I did some research, and the problem persists even with upgraded Nuxt and pnpm. The cause of the problem is the removal of the alias for pinia in https://github.com/vuejs/pinia/commit/65031ee77ed46a34bc2359223e24c7944e840819 I needed that change to work in other scenarios so I will investigate this further. In the meantime, here is a workaround: add an alias to your nuxt.config so pinia is resolved correctly:
Or exclude pinia from vite optimization:
@danielroe I would like some help with this matter: in my tests, I have two copies of pinia in non monorepo nuxt applications. I still don’t understand why this part of the Pinia module is so flaky, and I suppose it’s more of an issue of Vite than Nuxt. But I imagine you have seen this issue often enough to guide me in the right direction (and add a note comment so my future self does not forget 😅)
Hi all,
I am still encountering this issue, which is identical to #2837.
The problem occurs after upgrading
@pinia/nuxtfrom0.5.1to0.9.0. It specifically happens when making GraphQL requests usinguseAsyncQuery (Apollo client)oruseQuery().Any help or insights would be greatly appreciated!
BTW, i tried everything i found so far!
Can this issue be reopened? It still persists after upgrading to
@pinia/nuxt@0.8.0and regenerating a fresh lockfile, I’m not entirely sure it’s the same issue as above.I’m also using a
pnpmmonorepo, and I already hadpiniaas a dependency. The only way to resolve was downgrading to@pinia/nuxt@0.5.5.Thanks!
Hello, today I’ve updated from v0.5.5 to v0.7.0 and couldn’t run the project.
This is the error I’m receiving “[nuxt] [request error] [unhandled] [500] Cannot find module ‘/.output/server/node_modules/pinia/dist/pinia.mjs’ imported from /.output/server/chunks/build/server.mjs”
and when I check the file in node module there is only pinia.prod.cjs file.
nuxt: 3.13.2
also I use pnpm
Thank you
@rylanharper @maxdzin just thumbs up the issue, that way mantainers can sort issues and find the most searched ones 😉
This could be a special case for me but I was able to fix it.
I had /main-nuxt /layer-nuxt
main-nuxt used layer-nuxt. In layer-nuxt I had one store in /stores installed was nuxt-pinia and pinia (no idea why i installed pinia and the nuxt pinia but it was/is and it seems to work prod/dev)
package.json: “@pinia/nuxt”: “0.10.1”, “pinia”: “^3.0.1” Installed in both nuxt apps
How I fixed it: In the /stores stores of the layer-nuxt I was using
import { defineStore } from 'pinia'Removing this solved the issue completely.
@mobayen I have been experiencing the same. I’ve created a new issue #2872 with reproducation repo.
I also had to do this using a yarn monorepo. I’m not sure what is causing it, but it’s definitely a bug.
Maybe try the following? In
node_modules/pinia/dist/pinia.mjschange the definition ofshouldHydrate(on line ~1211 by replacingobj.hasOwnProperty(skipHydrateSymbol)with!Object.prototype.hasOwnProperty.call(obj, skipHydrateSymbol). The payload-plugin is the reason why it works on 0.5.5 but not 0.6.0.I tried to add
console.log()toshouldHydrate(to verify that the apollo response is the object that causes the issue, but that caused the server to hang for some reason. 😕I’ll try to put together a repro for you over the weekend, much appreciated!
this should now be resolved in latest nuxi! 🎉
https://github.com/unjs/nypm/releases/tag/v0.4.1
That error is fixed by installing pinia
I think that to fix this we might release a new version that removes the compatibility with Vue 2.6 but keeps Vue 2.7. This will allow removing some peer dependencies that nom isn’t able to support (like other package managers do)
I’m still not 100% sure of the fix being the right solution so I will keep this open until then
Can confirm. This is breaking all my Nuxt projects that use Pinia 😢