Quasar v2 (Vue 3) - released!

[rstoenescu]

Quasar v2 is out! Read our announcement.

Is v2 stable?

YES

The plan

Our main focus at the moment is shipping Quasar v2 with Vue v3.
The plan is to not introduce any breaking changes, unless forced by the vue 3 / vue-router 4 architectures.

Affected Quasar packages: "quasar", "@quasar/app".

Rough schedule

• First beta: "quasar" v2.0.0-beta.1 & "@quasar/app" v3.0.0-beta.1 - Jan 2021
• Stable releases: "quasar" v2.0.0 & "@quasar/app" v3.0.0 - Q2 2021

The code

The branch currently holding Quasar v2 is called dev (was previously vue3-work).

Donations

If you want to speed up the development of Quasar please consider donating to the project. With proper funding, it allows more of the team to work on the project in a much more dedicated manner.

Donations - https://donate.quasar.dev

If you're in a company and using Quasar for commercial projects, explain to your management the importance of monthly donations (eg. $200+) for open source projects: you're the one using it every day and this makes you the best suited person to convince them. Be creative! :slight_smile:

Quasar is saving your company tens of thousands of development hours (quite literally), which in turn is a pretty high money savings. Consider giving back a part of those savings to refuel the project itself 😉

Update: June 21st 2021

Quasar v2 stable (with Vue.js 3) has been released! Time to party!
#9734

Update: June 19th 2021

Next release is v2.0.0 stable.
Branch vue3-work has been merged into dev. The Qv1 work will now be done exclusively on the new v1 branch.

Update: April 27th 2021

We have passed the final major milestone: Quasar CLI now ships with Webpack 5, which was badly needed to support Node 13+. Faster build speeds and lower memory usage.
We're just a few small steps away from getting Quasar v2 out of beta!

Update: April 4th 2021

The last Quasar CLI mode left to be enabled, which is SSR, is now also available.
Here is the link to the upgrade guide on SSR.
We are targeting for a 2 weeks testing period for SSR mode then we will release the official stable version of Quasar v2.

Update: February 16th 2021

We're close to the stable release. The only thing remaining is the SSR support. Quasar is SSR ready, however we're only going to enable SSR support as soon as these Vue3 SSR bugs (critical for us and your experience) are solved:

• [ssr] Hydration error with <component :is="someVar"> vuejs/core#3244 redirected to bug with vue3 ssr and dynamic component vuejs/core#2863
• @vue/server-renderer <img> inside slot leads to double import of same asset vuejs/core#2386
• [ssr] hydration error with comment and null value variable interpolation vuejs/core#3245
• [ssr] Hydration error with animateTransform node vuejs/core#3243
• [ssr] Error with KeepAlive: Cannot destructure property p of 'undefined' or 'null' vuejs/core#3255

Update: February 10th 2021

SSR mode is ready (UI and CLI-wise) to be released. Unfortunately, there are quite a few Vue SSR bugs that need to be fixed before we enable the build mode for Quasar v2. We are in the process of reporting them and we'll start collaborating with the Vue team to help fix them.

Update: January 11th 2021

Hi All,

There are still some things being worked on for Quasar v2, but mainly we're now writing the migration guide. Our target for release of the public beta is within January 2021. The new version is based on Composition API. But it's not just a port to Vue 3. There are lots of significant performance enhancements in Quasar's algorithms too! You'll love it!

Unfortunately, the first beta release won't include SSR support, due to missing some upstream features in Vue 3, which we'll contribute to via PRs. We'll release SSR support during the beta stage lifecycle though.

We're also trying to integrate Webpack 5 support into the @quasar/app v3 release, but if we are unable to get this done (ie: external dependencies and such) then we'll shoot for @quasar/app v4 release.

Stable release will be anywhere within Q1 2021, but as is the case with OSS, it will be ready, when it's ready. And of course, it will be ready when we know the quality is high enough to meet both your expectations and ours.

In the meantime, the wonderful framework you've come to love is still here and you don't have to wait for Quasar v2 to start a new project with Vue 3's major new feature (i.e. using the composition API). Of course, if you choose to hold off on Vue 3 features, we'll make the upgrade as easy as possible for you. That's a promise. :slight_smile:

The Quasar Team

[ontwikkelfabriek]

@rstoenescu
Will the codebase of Quasar v2 with Vue 3 be rewritten in TypeScript just like Vue3 is?

[IlCallo]

Quasar v2 will lay the fundations needed for a Composition API + TS + tests incremental migration, which will take place during Quasar v2 lifecycle.

Quasar v3 will probably be released when this incremental migration is completed.

[chintan-mishra]

Those who downvoted. Or are planning to do so. READ THIS.

Providing a stable API that maintains as much compatibility as possible requires time, effort, and capital. This is not to say that things won't break when moving from v1->v2. But the collateral effect of migrating to a complete TS based Quasar will be too large on the wider community. Thus, as an engineer I am following the exact same steps mentioned here. I am migrating some code of my very large Quasar v1 with Vue2 to TS and by the time v3 arrives we will have the whole community using TS.

Finally, if you are creating a new project and want to use TS then just add TS support when creating the application using the wizard.

[rstoenescu]

Maybe an additional important information. For app developers it won't matter whether Quasar is written in TS or not. Sure, the autocomplete will work a bit better, but you as a developer are NOT required to also use TS in your app.

[matt-spx]

Are there any plans or ideas to support vite in quasar v2?

[zhengycsh]

desire

[leannc]

Is the beta version available now ? Waiting for this~

[rstoenescu]

Hi everyone,

Sorry but we'll have to delay the beta version due to vue-loader which has some SSR features not implemented yet. We cannot release a beta version until SSR is fully solved or else we might introduce breaking changes during this beta stage -- and we want to avoid this at all costs.

The new schedule is:

• First beta: "quasar" v2.0.0-beta.1 & "@quasar/app" v3.0.0-beta.1 - 2020/12/15
• Stable releases: "quasar" v2.0.0 & "@quasar/app" v3.0.0 - 2021/01/30

[bzd2000]

Is there an Alpha release?

[rdev06]

Can I use branch vue3-work for learning Quasar2 with vue 3 purpose?

[bzd2000]

Tried to build the vue3-work branch, but don't see how to build to app package.
I followed to instructions in the contribution guideline, but it seems only for the UI package.

Are there instruction on how to build the App package?

[BenHayat]

@rstoenescu
I had recently made a suggestion on next Quasar version # in the forum. I'd like to echo that here as well.

Most third party products try to follow the main product version # to make it more clear to the customers. For example, now the the new .Net 5 is out, most of the third party libraries, they use # 5 as well. Like Entity Framework 5 or ASP.Net 5 and etc.
In Vue, Vuetify and PrimeVue are doing the same following V3.
My suggestion is to skip Quasar V2 numbering and go straight to V3. This way, new prospects won't get the wrong impression that Quasar V2 is for Vue 2.
Hope this helps.

[smolinari]

@BenHayat - Unfortunately, that isn't going to work. Quasar/UI v2 is planned to be purely a port to Vue 3. Quasar v3 is planned to be a further and important evolution of Quasar, also built on Vue 3. See the dilemma? 😊

Scott

[BenHayat]

@BenHayat - Unfortunately, that isn't going to work. Quasar/UI v2 is planned to be purely a port to Vue 3. Quasar v3 is planned to be a further and important evolution of Quasar, also built on Vue 3. See the dilemma? 😊

Scott

@smolinari
Now it all makes sense. Quasar V2 and Quasar V3.
I didn't know this information.

Thank you Scott!!!

[layanto]

Will Quasar V2 and V3 consider supporting Pinia as alternative to Vuex? I think the API for Pinia is similar to the proposed API for Vuex 5 and has better typescript support.

[smolinari]

@layanto - Vuex isn't directly a part of Quasar. It's only suggested during project creation via the CLI. In the end, you can use whatever state management package you'd like, as long as it works with Vue.

Scott

[layanto]

What about accessing store from boot file if using Pinia as state management instead of Vuex?

[smolinari]

I believe Quasar will inject in anything found under src/store. @layanto Don't quote me on that though. 😁

Scott

[rstoenescu]

Teaser: https://codepen.io/rstoenescu/pen/dypbRPL?editors=111

[JulesNeck]

This looks really promising. The new quasar version will be my favourite christmas gift. Thanks Razvan for your magnificent work!

[BenHayat]

What is the significance of this teaser, beside these fact that Quasar is running in V3? Am I missing something from looking at those cards?

[danielfaust]

@BenHayat That finally the migration of that old AngularJS-webapp to Vue3+Quasar is within reach?

[francoism90]

@rstoenescu Quasar V2 looks good so far! I'm using the AirBNB linter, capacitor and loving the Vue composite API.

[jonathanpmartins]

I'm just passing by to congratulate you for the excellent work!

[rabbiveesh]

Forgot to post some updates here. So:

• the NPM v7 issue is solved
• we'll try to write a guide on vue-compat (@jacksongross )
• creating a project folder with any of the available options will now not result in a lint error

Preparing v2.0.0-rc.1

Is there any news on the vue-compat guide? I'm itching to try out v2, and need to do the migration build so I can upgrade smoothly

[soulsam480]

Amazing work @rstoenescu

[francoism90]

@rabbiveesh How exactly does it work? I rewrote the project in Vue3, just because the Composite API works so good and I could remove ugly things like mixins.

I was very skeptical on the Vue3 changes, but so far I really like them. :)

[IlCallo]

Small heads up on what has been happening lately regarding Quasar v2 release.

We have been postponing Qv2 stable release (eg. we planned to release RC on 28th of May) due to some last minute problems with some upstream deps.

In particular, latest Sass releases added deprecation warnings for some widely used features, and this generates A LOT of warnings.
Even if it's not technically a breaking change, it's an horrible DX not related to Quasar.
To avoid it, we would need to refactor most of Quasar CSS, which will result into a breaking change for Qv2 early adopters which went through the beta, and we don't like this option.

On the other side, there seems to be no way to silence those warnings yet.
There is an undergoing effort to silence at least the warnings coming from Quasar code itself (sass/sass#3065), but this solves only half of the problem.

Anyway, we're now into RC phase, we'll continue to work to solve this and other issues during RC phase, thanks for your patience and support <3

[xizprodev]

Is there a problem with quasar vue 3 and webserver?
On my old admin build on quasar with vue 2 i have this configuration for devserver:
devServer: {
public: 'https://admin.local',
https: false,
port: 8080,
open: false // opens browser window automatically
},
And it works very good, but when i upgrade to quasar vue 3 (i create a new project with quasar create --branch next and move some files from old src to new src folder) i got lot of errors in console WebSocket connection to 'wss://admin.local:8080/ws' failed:

[IlCallo]

Hi @xizprodev may I ask you to create a repro and open a new issue?
Underlying webpack-dev-server advanced by a version and some things changed, so you should probably start by checking that out if you have problems with it

[maggie44]

Is there a problem with quasar vue 3 and webserver?
On my old admin build on quasar with vue 2 i have this configuration for devserver:
devServer: {
public: 'https://admin.local',
https: false,
port: 8080,
open: false // opens browser window automatically
},
And it works very good, but when i upgrade to quasar vue 3 (i create a new project with quasar create --branch next and move some files from old src to new src folder) i got lot of errors in console WebSocket connection to 'wss://admin.local:8080/ws' failed:

Check out #9466

[rulrok]

Just a curiosity: is the performance improvement of q-img from v2 going to be ported eventually to v1?
From what I read it seemed quite important to just be left out.

[IlCallo]

QImg optmizations (as others Quasar v2 optimizations) rely on modern features which IE doesn't support.
Since Qv1 must be IE compatible, it's not possible to backport those optmizations

[rstoenescu]

Preparing for the v2.0.0 stable release.
Branch vue3-work has been merged into dev. The Qv1 work will now be done exclusively on the new v1 branch.

[rstoenescu]

The big announcement has come. Time to close this ticket 🥇

[rodrigoslayertech]

My old project is using multiple Quasar extensions. I can't migrate yet. Quasar Extensions are taking a long time to port Quasar 2.0.

[francoism90]

@slowaways What kind of entensions are you using? I have migrated to other solutions when the extension wasn't available anymore.

[rodrigoslayertech]

@francoism90 QIconPicker, QPDFViewer, QCalendar...

[francoism90]

@slowaways

https://github.com/quasarframework/app-extension-qpdfviewer/releases/tag/v2.0.0-alpha.2
https://github.com/quasarframework/quasar-ui-qcalendar/releases/tag/v4.0.0-beta.4

QIconPicker seems to be compatible and maintained?

[rodrigoslayertech]

@francoism90 Yes, but waiting release version.

[francoism90]

@slowaways You could already start developing in Quasar v2 as most extension breaking changes will probably be minor. I also started with the beta's (including non Quasar extensions) and could easily move to the stable builds when they become available.

[hawkeye64]

@slowaways QIconPicker (@next branch) will be released soon

[melroy89]

Thank you so much!

[zenflow]

#7836 (comment)

we'll try to write a guide on vue-compat (@jacksongross )

@rabbiveesh @jacksongross Any guide/resources on this? Or any luck implementing it? (i.e. is it possible?)

[IlCallo]

@zenflow
Have you checked out https://github.com/vuejs/core/tree/main/packages/vue-compat#readme ?
If yes, did you had any problems with it? It's not clear from your question

[zenflow]

@IlCallo Yup, I have. I was just wondering if there were any additional tips or info (caveats?) on doing it with Quasar. I'm attempting it now, so I will report back here, and open issues if I come across any.

[IlCallo]

Thanks! We appreciate when people give back to the community :D
If there's a dedicated issue, please use that one to post feedback.
If there isn't and you hit some problems, please create a new one so we can avoid spamming all the people subscribed to this issue