@ryan nope, I didn’t
maybe I could give it a try

v 0.15 of course

Is there a way to enable ‘webpackChunkName’ for code splitting in quasar config?

What I’m doing in my routes is basically trying to put everything that goes under /auth route and all of its children into the same bundle:

export default [
{
path: ‘/auth’,
component: () => import(/* webpackChunkName: “auth” / ‘layouts/auth’),
children: [{
path: ‘login’,
component: () => import(/ webpackChunkName: “auth” */ ‘components/auth/AuthLogin’)
}, {
path: ‘’,
redirect: ‘login’
}]
}
]

After running qusar buiild, I’d expect to see js/auth.41e0cf096add72be2a2e.js bundle created

Thanks!

https://github.com/quasarframework/quasar-play/blob/master/src/components/showcase/progress/loading.vue
this is a good example of how to do it from within a .vue module

@ryan nope, I didn’t
maybe I could give it a try

Well, managed to do this using QWindowObservable.
Basically, using vuex we can do something like this:

onResize (width) {
this.updateIsSm(width < 992)
}

and then map getter to a computed property

Hey everybody!

Wanted to upgrade to v0.15-beta.12 my existing quasar project (currently 0.14.7).
Bumped the version in package.json, did npm install, then npm run dev.

Got the error straight away:
These dependencies were not found:

• quasar in ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/App.vue, ./src/main.js and 13 others
• quasar/dist/quasar.ie in ./src/main.js
• quasar/dist/quasar.ie.mat.css in ./src/main.js

To install them, you can run: npm install --save quasar quasar/dist/quasar.ie quasar/dist/quasar.ie.mat.css

Well, I went to my main.js and commented out IE11 support to see if that helps:
// IE11 Support
// require(quasar/dist/quasar.ie)
// require(quasar/dist/quasar.ie.${__THEME}.css)

Then did npm run dev again:
This dependency was not found:

• quasar in ./src/main.js, ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/App.vue and 13 others

To install it, you can run: npm install --save quasar

Hm, this seems to be a bit weird as quasar package (npm info quasar) has nothing to do with the quasar-framework package that is being used.

Is there anyone that did actually manage to migrate from an old (v0.14) version of quasar to v0.15?

Thanks!

Eugene

Hey, guys!

Not sure what is the best approach here…

Wanted my button to have full width on small screens only, would that be possible to do something like:

:class="{‘full-width’: $q.isSm}" ?

Thanks!