Hey @spanners welcome to Quasar.
You will be in no way tied to use Stylus, it is true that the internal components use Stylus as CSS pre processor, but you can choose whatever you like for your Quasar app.
The docs explain how you can switch the pre processor on the example of SCSS.
Also, if somehow there are issues with Stylus that are not resolved upstream, I am certain that Quasar will adopt accordingly.

If you look at the contributor graph at GitHub you will see, that there are actually a lot of people that contribute to Quasar and there are two lead developer, namely @rstoenescu and @pdanpdan

I can only recommend you to join our Discord chat at https://discordapp.com/invite/5TDhbDg where the community is way more active. From the forum you could get a false impression about how much people care for Quasar.

Hopefully I could resolve you concerns, otherwise I am glad to answer additional questions.

The themes are only referring to the style guidelines used to create them.
The “Material theme” sticks to the Material guidelines from Google and the “iOS theme” to Apple Human Interface guidelines.

You can, however, choose any theme in any browser/device, the compatibility is the same.
Due how the build process works you cannot switch themes during runtime (also this would ship lots of unneeded resources for your customers), this is why you have to set the theme at build time.

Hey @kiranvasi
we are currently working on integrating SSR into Quasar. The roadmap that we intend to ship this feature in v1 is still valid.
The template you are referring to will be deprecated, so until you are not in total need for SSR in your app right now you should wait for v1.
Currently, we can not give a real estimate when v1 will be ready, but probably it will take some more time because we have to make sure that v1 really is stable.

Hey André,
you can install a specific version of Quasar cli using npm install -g quasar-cli@version.
In your case that would be npm install -g quasar-cli@0.15.2.

But please note that there are two versions of Quasar CLI.
One that is installed globally and one that is installed in your project.
The one in your project automatically installs to the same version your friend installed it.

I would recommend updating your Quasar version to the latest version by running npm update quasar-cli inside your project.

Also best luck on your project, make sure to share your results on the forum or on Discord

Hey, there is no “official” way, but I can tell you what we did with our API endpoints.
We have a directory /src/api. In this directory, each file represents an API endpoint.
All files extend a simple REST client which uses axios and has methods like list, create, update and delete.

The crucial point here is that each file exports a class by default.

// Simplified example
// src/api/demo.js
import axios from 'axios'

export default class DemoClient {
  list () {
    return axios.get('/my/api/endpoint')
  }
}

Also, note that the methods return the axios promise.

Not in your components you can import your client and use it.

// demo.vue
import  DemoClient from  'src/api/demo.js'

export default {
  data () {
    return {
      demoData: []
    }
  },

  created () {
    DemoClient.list()
      .then(response => {
        this.demoDate = response.data
      })
  }
}

@leopiccionia No it would not be reactive.
But in this case, it wouldn’t matter because you certainly would not edit the quasar.conf.js during runtime

@leopiccionia You don’t need a mixin for this.

Assuming you had access to the config (which is not easily possible because it is a function which requires a context), you could have an app plugin like this:

import config from 'quasar.conf.js' // This does not work

export default ({ Vue }) => {
  Vue.prototype.$config= config
}

The problem is that quasar.conf.js requires a context that is passed.
Here is the source from quasar-cli which parses the config: https://github.com/quasarframework/quasar-cli/blob/dev/lib/quasar-config.js

Any special settings you wanted to read from that config file?
You could go the other way and import your custom config file (e.g. /src/config/index.js) in Quasars config file.

That’s really strange, it should be available on every VueComponent: https://vuejs.org/v2/api/#vm-emit

Is it only on this component or also on others?

Please do not double post questions!