Pinia Devtools Wishlist

I think it would be nice to gather feedback about how to improve the existing devtools or reporting bugs.

If you find something that you think can be improved, a screenshot is usually enough to help describe the improvement. I want to use this issue to track those improvements.

• Display all getters in the Inspector View (🍍 Pinia (root))
• Allow calling $reset() directly from the devtools (Using actions + adding this in formatStoreForInspectorState(). This should only appear in the inspector view, next to the state property.
• Add a settings panel (https://devtools.vuejs.org/plugin/plugins-guide.html#plugin-settings)
  • Use emojis in messages (defaults to true)
  • Disable “x store installed” message https://github.com/vuejs/pinia/discussions/1070
  • Show stores in components (defaults to true) This can be set already in plugin settings
• Time travelling
  • Changing the current state from the timeline (should not add new events)
  • Use a patch-driven approach like in Vue Devtools for perf reasons
• Clear ans concise information about single mutations
• Allow prod devtools (with less information because events might not be there)
• Clicking on a store in pinia devtools should make it available as a global variable

Please do not use the issue to report bugs, use the Discussions for help or open an issue with a boiled down reproduction for bugs.

[EmmanuelQ]

Would be great to show the actual state property being modified eg here we know the store is pokedex but i’d like to know the state property that “set” is targeting.

[Caruki]

When using the Vue Devtools in production mode with the provided flag VUE_PROD_DEVTOOLS the pinia plugin is not showing up. Even though other plugins (i18n or router) are. Is this a known issue with pinia?