I’m sorry but this is not an usual problem so your guess i as good as mine.
If you have issues with the port being already occupied (this should give you an error message saying exactly that) check for any running node processes in task manager.
Can’t help but notice you have it within xampp folder, could that have anything to do with it?
Quasar v0.15 will be out this month, so you could just be patient and wait for release.
If you want a sneak peek her is what I did:
git clone https://github.com/quasarframework/quasar.git
this should show you the dev version of quasar v0.15
Lots of new goodies!
This is nice! However, I inverted the colors (gray spinner and white background) because otherwise it was not visible (white spinner over white background) since div#q-app (the background) has height of 0px.
Take a look here for more details on importing icons. Quasar icons are provided by quasar extras so take a look there. No need to make your own quasar fork. Also, note that v0.15 is coming out this month with a big focus on user customization
@benoitranque for me this solution would lead to bad practice as I have all kinds of logic to determine whether the the left and right drawers should be opened or closed in a Vuex mutation. This way i would be forced to put that logic in every deep component that can change the sidebars rather than one succinct commit call. The documentation gives an example of using v-model to handle the sidebars and it works perfectly in desktop mode. So I am seconding @dsahoo that I also think this is a bug.
Allright, it’s solved, at least for me.
I was importing the quasar style in a component (bad idea, don’t know why I did that in the first place) as I saw it referenced twice in the head section of my page (doesn’t webpack check on double references ?)
Now everything is working fine.
Sorry for that