if we want some HMR magic for it is related to hot reload - if you want the store to reload only a single module on changes during development instead of trigger rebuild.

And yes, you can organize the store however you want - put everything in index.js, or on the same level… it’s up to you. Quasar scaffolds very granular setup at start, but you can definitely reorganize it for your needs. I tend to have just per-file modules, because they are usually pretty small in my projects. In the end store is just a bunch of JS objects and functions that you put inside the Store constructor. There is no restriction on how you organize them.

You can reset the store with some mutation nulling all variables like Max said. I often use dynamic modules and just register one on login and unregister it on logout. That way I can just throw out all the data easily.

Did you try it? Does it just work or you need to install something else? (I use WebStorm and it does all this automatically)

This feature just came out check the announcement

@mesqueeb
Question 1: Yes, they differ. Only Major version should stay the same…
Question 2: I had a problem with that, too. You need to convert it to usage of Quasar plugins - store is injected in them. Once you create store, you can also name-export it, too… But I would try to avoid that, because you would need to do lot of null-checking.