-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
help: Pinia stores are empty in devtools #724
Comments
Please provide a minimal reproduction. Thanks. |
Happening to me too in Chrome (incognito also doesn't work), working in Firefox and Edge. Can't really provide a reproduction since it worked fine for months and just seemingly randomly stopped working |
I upgraded from Nuxt 3.13 to 3.14 and now I also see "No Data" |
does not repoduce for me. A friend of mine got the same problem and we discovered that it is (atleast for him) related to the chrome extension vue dev tools. Removing vue devtools fixed it for now, or opening the vue devtools pinia tab. Ill try to reproduce today :) |
Reproduction:
|
@OrbisK I just tested with Vue Devtools extension and it looks like that is the problem. If Vue devtools ir enabled then it breaks. But it happens starting with Nuxt |
@martinszeltins @OrbisK @manniL Thank you for your answers! I completely forgot about this issue. I recently installed the Vue Devtools extension, and now I use it to check my stores. However, I want to mention that the problem appeared for me before the extension was installed. Disabling the extension doesn’t solve the issue for me either. |
Disabling the vue extension worked for me, thanks all. |
📚 What are you trying to do?
Hello!
We just initialized our monorepo with three nuxt projects in it. The problem is that we use pinia in our projects and if I open devtools, I see the pinia tab, but all the stores inside are empty. I tried to google it out, but I cannot find anyone with the same issue. Any ideas on how to solve this?
🔍 What have you tried?
No response
ℹ️ Additional context
No response
The text was updated successfully, but these errors were encountered: