Or did you forget to add “addressbar-color” to the list of your custom plugins?
http://quasar-framework.org/guide/app-plugins.html

Yes, this should work in the dev build. When you refresh it? Do you mean reload the page?

Do you mean all-caps or first-letter caps?

That is really sweet @Fernando2684 - nice idea. As far as your code goes, there are several places where you could clean it up, first and foremost you should always aviod type conversion. You should get in the habit of using === and !== instead of == and !=. This is what Douglas Crockford has to say about it (from this SO post )

'' == '0'           // false
0 == ''             // true
0 == '0'            // true

false == 'false'    // false
false == '0'        // true

false == undefined  // false
false == null       // false
null == undefined   // true

' \t\r\n ' == 0     // true

Here is a little update to show you that it also works as expected: https://jsfiddle.net/7fuckt8s/ (It seems I win the jsfiddle lottery!!!)

That is ugly! I would probably do something on mounted (and upgrade as soon as possible to v0.16)

mounted () {
    console.log('The instance has been mounted')

    // Note that mounted does not guarantee that all child components have also been mounted.
    // If you want to wait until the entire view has been rendered, you can use vm.$nextTick
    // inside of mounted:
    this.$nextTick(function () {
      // Code that will run only after the
      // entire view has been rendered
    })
  },

Here is a great resource for you: https://github.com/LeCoupa/awesome-cheatsheets/blob/master/frontend/vue.js

@limjackson SSR work is being done with 0.17 (which is currently in a prerelease) and yes, hopefully it should all just work.

@Hawkeye64 @silentcoast - I wrote about this on a quasar issue:

https://github.com/quasarframework/quasar-cli/issues/122#issuecomment-391266544

the easy fix is to up the amount of memory node has available:

$ NODE_OPTIONS=--max_old_space_size=4096 DEBUG=v8:* npm run dev:pwa

where dev:pwa is “dev:pwa”: “quasar dev -m pwa”, in package.json

If you run up against the strange code 3 exit error, then you are probably working in an environment that does not have an x-window and are running quasar dev. The solution to this is to make a setting in your quasar.conf.js:

    devServer: {
      open: false
    },

anybody having problems resolving quasar in jest, use this:

    "moduleNameMapper": {
      "quasar": "quasar-framework/dist/umd/quasar.mat.umd.min.js"
      ...

@camilo - I don’t do SO much with stylus, but a quick look at the github repo showed that their use of border didn’t declare a color. Just a guess, but maybe you could try:

.border
  border 1px solid 
  border-color $item-separator-color