vuedevtools vuex tab does not work via `quasar build`
See original GitHub issueDescribe the bug
If you browse a prod SPA app built with quasar build
, the vuex tab of vuexdevtools will not work. You get the message No vuex store detected
, whereas in a vanilla VueJS build it works.
Codepen/jsFiddle/Codesandbox (required)
It is not possible to demonstrate this bug on these platforms. The bug ONLY OCCURS if you quasar build
and then serve that via a web server and browse to it that way.
None the less I’ve shown the code required here: https://codesandbox.io/s/vuedevtools-vuex-tab-setup-31v4l
To Reproduce
- In both vanilla Vue and Quasar it’s possible to set up vuedevtools to work on prod. (i.e.
quasar build
). In vanilla vue, you just need theVue.config.devtools
. In Quasar this requires a boot file like this:
import { boot } from "quasar/wrappers";
export default boot(({ Vue }) => {
Vue.config.devtools = true;
});
- Then this must be enabled in
quasar.conf.js
:
boot: ['devtools'],
- Enable the default vuex store by uncommenting lines 4 & 20 in
src/store/index.js
- Add some state to the store in
src/store/example/state.js
- Then you need to build it:
quasar build
- Then you need to serve that via a web server (exercise for reader)
- Then browse to it
- Open devtools, click vue tab to get vuedevtools
- Click on the
vuex
tab in vuedevtools - Click on the
Base State
mutation to load the state into thevuex
viewer.
Expected behavior It should show the vuex state
Screenshots
Two screenshots. One shows it working via localhost (i.e. via quasar dev
)
The other shows it not working via quasar build
Platform (please complete the following information): OS: Mac OS Catalina 10.15.7 Node: v12.6.0 NPM: 6.14.8 Yarn: 1.22.4 Browsers: Chrome Version 86.0.4240.80 (Official Build) (x86_64) iOS: N/A Android: N/A Electron: N/A
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top GitHub Comments
Those who’ve upgraded to q/app v2.1.2, please do a quick upgrade to v2.1.3. process.env.DEBUG should be process.env.DEBUGGING.
Fix will be in @quasar/app v2.1.2