Here is my Alfred workflow for fast and easy documentation search:

https://github.com/mstaack/alfred-quasar-docs/releases

best calendar componet out there!

whats your exact problem? please share some code and infos

just an idea, i used this to download a file (item.download is the download url)

      downloadItem () {
        window.location = this.item.download
      },

please post a quasar info output

i would try to import the router where you need it:

import router from '/router/index';  //replace with your correct path

changing /src-electron/main-process/electron-main.js is fine!

consider using mainWindow.maximize()

can you create a codepen with your issue? https://codepen.io/rstoenescu/pen/VgQbdx

have you searched online for a solution?
-> http://tommylee.co/tutorials/fixing-hot-reload-vagrant.html

you might also have to customize the webpack config to specify the new host, but dont know for sure

hey @miromanyth

highly recommend not to try that!

quasar has a full flexbox based layout/grid system

check -> https://v1.quasar-framework.org/layout/grid/introduction-to-flexbox

@chyde90 valid point

isnt swiping only a mobile thing? how would you swipe on desktop?

your codepen is always reloading currently, cant check your code. maybe its an issue on codepens side

@Recke Autocomplete and QChipsInput were migrated into https://v1.quasar-framework.org/vue-components/select

also checkout the https://v1.quasar-framework.org/start/upgrade-guide

Quasar usage of vuex is not different. It’s all basic vuejs functionality and resetting the store could be done by any action/mutation clearing/nulling your variables.

Any specific problems doing that?

this is not part of quasar. its a custom implementation only for the docs currently afaik

did you enable IE support in quasar config?

can you create a reproduction of your issue? maybe with https://codepen.io/rstoenescu/pen/VgQbdx

@paul also have a look at
https://v1.quasar-framework.org/quasar-cli/cli-documentation/handling-webpack#Webpack-Aliases

there are most of the important aliases already built in

should be coming from webpack’s resolve/alias feature