App Build Commands     


Starts a Node.js local development server. See API Proxying For Dev for more details.

# run development server (with default theme)
$ quasar dev

# run development server with specific theme
$ quasar dev mat
$ quasar dev ios

# dev server with QR code
# scan QR code with Quasar Play app
$ quasar dev -p
$ quasar dev --play
$ quasar dev mat --play

While developing with the Dev Server you will have:

Generate .vue Components

After creating an App folder with the CLI, you’ll have a folder named /templates inside the generated app folder, which contains templates for: layout, page, or a generic Vue component.

You can generate components for your App in your /src folder:

# get available Component templates
$ quasar new -l
$ quasar new --list

# generate .vue file from a Component template
$ quasar new component Hello

# generate .vue file from a template to a subfolder
$ quasar new layout layout/about/help/Hello
# the above creates src/components/layout/about/help/Hello.vue

You can also add your own component templates. Quasar will be able to handle them too.

Serve Static-Content Folder

You are able to create an ad-hoc web server to serve static-content web files from a folder. Browser sessions are automatically refreshed when content changes. User click/scroll can be synchronized.

This command comes in really handy after building your Quasar App for production. The /dist folder contains files that are meant to be served with a webserver. So here you go:

# Serve current folder:
$ quasar serve

# ..or serve a full or relative path
$ quasar serve dist
$ quasar serve ./dist
$ quasar serve /work/quasar-app/dist

This command does not rely on Quasar Framework. Any folder with any web content can be served.


Build assets for production.

# build for production
$ quasar build

# build for production with specific theme
$ quasar build mat
$ quasar build ios