MY 2 Cts: I would help to have the estimated timeline described above published in the announcements. This is an important information that should be more readily available (easy to find) to the community.

It appears to work fine in my test app. It’s a tad verbose but works ok. At least, it supports Vue 3 & typescript. Still waiting to know quasar’s roadmap on Vue 3 & getting worried.

Remains to be seen if the Quasar plugin is compatible with V3. So far I have not gotten any response on these posts

Found this statement in one of the discussions. Since I do write a PWA, Vue-CLI is no issue in my case. Will try this approach to facilitate the VUE 3 migration;

Disadvantages, due to current vue-cli 3 architecture:
no ability to “write code once then deploy as a SPA/PWA/Mobile & Electron app”; you will usually pick what you want to build (SPA or PWA – only) right from the start when creating the app with Vue CLI; even if vue-cli will support these
only SPA and PWA supported; can’t build Mobile or Electron apps as vue cli doesn’t support it; the smart algorithms behind Quasar CLI use more than one webpack config, which is not possible with Vue CLI
none of the features embedded in quasar.conf.js; for many, you’ll have to manually edit your src/main.js file
building/developing with one theme and switching to the other requires editing the vue config (in package.json or vue.config.js, depending on what you picked when creating the vue app)
you lose the ability to effortlessly upgrade your the Quasar version that you are using as with Quasar CLI; it will possibly require you to manually edit src/main.js to update to latest specs

With Vue 3 release around the corner now, what is the Vue 3 migration status for Quasar?

Vue CLI will offer a code migration tool. I am considering using Vue CLI to facilitate the migration process. However the current doc states: “Cross-platform support with Vue CLI is handled by community plugins. These are not tightly integrated with Quasar as with Quasar CLI and may have issues.”. What are these issues? Any steps you recommend to avoid such pitfalls?

@neilhoff I have done a complete test with the key UI elements of my app. It came out very quickly that Vue is not strategic for Ionic. They are focusing on React & of course Angular. The current “beta” implementation is very buggy & does not even support v-model. Look at the update activity on github: nearly nil with most of the sources being 2 years old. To be avoided absolutely.

One request for the fix: in the sourceMap, please do restore the template. At the moment, in one of the multiple sourceMaps generated, one does reflect my source code but the template code is removed from it.

importStrategy: “all” defeats all the tree shaking, so it is not suitable for me. Also, I am using the --modern switch to bypass Babel & compile in ES6. Does that have an impact?

@dineshtrivedi No, even after ditching out babel using the --modern switch. To be quite honest, this is becoming aggravating.

Since 1.+, I have seen the source maps multiplying for each component. By now, in 1.12 I only get in debug the transpiled sources, not my original ones. Is it due to webpack or does it originate in the quasar CLI? Will you offer an option to return to the single original source code map?

@dobbel : Adding to this request: A IOS QDate & QTime would be quite welcome in the IOS world. Whereas none of my users seem to care about the look & feel of a quasar app in IOS, they are however confused by the Android Date & Time picker

Vue 3 migration overview for Quasar users.

As a sub-topic: Vue 3 will provide a migration plug-in, provided one uses the Vue CLI. What is Quasar recommendation to migrate the code?

After the last upgrade (V 1.8.5, quasar app: 1.5.3), I am getting multiple sourcemaps per page/component (8 in the example below); Only one does contain the relevant code (the others are generated by Quasar). Furthermore, the one relevant sourcemap does not show the template anymore.

Any explanation or solution?

SOLUTION FOUND: Auto import does work, BUT only if the import.quasar.js file generated in the .quasar folder is first DELETED manually.

Moving to Auto import works, BUT only of import.quasar.js file generated in the .quasar folder is DELETED manually.

SOLVED: Scoped an SVG style modifier I had in my code.

Removing the label does not solve the issue

I tried & I cannot reproduce it in codepen. It only happens within the context of the full app.

In your test, are you using the label, as I do?

<q-slider class=“col-5” v-model=“aspOrb” :min=“0” :max=“16” :step=“1” :label-value="‘Orb:’+aspOrb" label-always color=“light-green” @input=“filterChanged”/>

Both include an SVG focusable element that could be the issue:

<svg focusable=“false” viewBox=“0 0 20 20” width=“20” height=“20” class=“q-slider__thumb absolute”><path d=“M 4, 10 a 6,6 0 1,0 12,0 a 6,6 0 1,0 -12,0”></path></svg>