Starts a Node.js local development server. See API Proxying For Dev for more details.
# run development server (with default theme)
While developing with the Dev Server you will have:
- The ability to develop on your phone with Quasar Play App
- The Webbpack + vue-loader for single file Vue components
- State preserving hot-reload
- State preserving compilation error overlay
- Lint-on-save with ESLint
- Source maps
After creating an App folder with the CLI, you’ll have a folder named
/templates inside the generated app folder, which contains templates for:
page, or a generic Vue
You can generate components for your App in your
# 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.
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
- HTML minified with html-minifier
- Unused CSS removed with PurifyCSS
- CSS across all components extracted into a single file and minified with cssnano
- All static assets compiled with version hashes for efficient long-term caching, and a production index.html is auto-generated with proper URLs to these generated assets