Documentation on how to import components just using quasar-framework in existing application

This does not exist at all and I am needing to hunt through the source code / install the CLI to try and set it up…

Copying some of the code showing how to instantiate Quasar from the template app, I have:

import App from './App.vue';
import Quasar from 'quasar-framework';

Vue.use(Quasar);

Quasar.start(function(){
    new Vue({ // eslint-disable-line no-new
        el: '#q-app',
        render: (h) => h(App)
    })
})

…but this errors on Vue.use:

Uncaught TypeError: _c is not a function
    at Proxy.render (quasar.common.js:1109) 

I just want to import <q-checkbox> haha! Is the component portion reliant on the whole Webpack/CLI build chain?

[rstoenescu]

@brokenalarms Quasar cannot be progressively added to a project. It’s an all or nothing deal.

1. If you’re not using a Quasar app template / boilerplate then yes, some of the files may appear as if they do not exist. But in the template they do.
2. All webpack rules are in the default app template.
3. _THEME is a token that gets replaced by webpack (if you’re using the default Quasar app template) so it’s not even a variable.

Bottom line, sorry but you cannot cherry-pick components from Quasar. All Quasar code is written with performance in mind, and this sometimes leads to not being able to cherry-pick. There are a lot of reasons, most important one being that Quasar is not just a component library. It deals with much much more. Themeing assumes there are some CSS classes attached to the body. Cordova needs its own JS to be included and Quasar deals with starting a Cordova app with the help of Quasar.start() method. Reasons after reasons. Won’t go into details as this would take me a day 😃

[BrennaEpp]

@brokenalarms Quasar cannot be progressively added to a project. It’s an all or nothing deal.

Bottom line, sorry but you cannot cherry-pick components from Quasar. All Quasar code is written with performance in mind, and this sometimes leads to not being able to cherry-pick. There are a lot of reasons, most important one being that Quasar is not just a component library. It deals with much much more. Themeing assumes there are some CSS classes attached to the body. Cordova needs its own JS to be included and Quasar deals with starting a Cordova app with the help of Quasar.start() method. Reasons after reasons. Won’t go into details as this would take me a day 😃

@rstoenescu Is this still the case? I’m trying to understand all what Quasar deals with in terms of Cordova and whether I can get rid of Quasar’s themeing while keeping other stuff, or if I can at least just use vue-cli-plugin-cordova + some quasar components