Skip to content
Permalink
dev
Switch branches/tags
Go to file
 
 
Cannot retrieve contributors at this time

Quasar Framework Roadmap

Where will Quasar be in one year, five years or ten years? It's up to you, the developers using Quasar.

You, the community, are Quasar. We listen to your opinions and your needs. Which is why we encourage you to directly contact us on Discord or submit Feature Requests. We carefully ponder on all the ideas and we decide along with the community what are the next steps to be taken.

Important!

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! :)

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 ;)

Support policy and schedule

All major releases are typically supported for at least 12 months. LTS support ends 12 months after the release of a new major version.

Version Status Released Active support ends LTS support ends
2.x Active 2021-06-21 After 2022-04-01 After 2023-04-01
1.x Active 2019-03-07 2021-04-01 2022-12-31

Quasar v0.x versions are no longer supported.

Major milestones

We are updating this section constantly in order to keep you up to date with our current (and new!) efforts.

The schedule may change based on unforeseen and/or out of the ordinary circumstances.

Q2 2022

  • ✌️ (DONE) Stable release of the new CLI based on Vite.js
  • ✌️ (DONE) Support Google Material Symbols (#13437)
  • ✌️ (DONE) Run automatic tests on Quasar UI via GitHub Actions for every PR #13432
  • ✌️ (DONE) Video tutorials for all Quasar components. Subscribe at QuasarCast to be notified when first-party advanced Quasar paid courses will be available
  • 🚧 (WIP) New Quasar website preview 🔥

Q3 2022

  • 🚧 (WIP) Quasar.Conf 2022 - 9th of July - Call for Proposals
  • Quasar v2 TypeScript projects created with Quasar CLI will have all files spawned in .ts format instead of .js for all Quasar modes (currently there are Quasar modes that have only templates in .js form) (#8572)
  • Gradually add more automatic tests to Quasar UI. We're searching for contributors, get in touch with the team on our Discord server if you're willing to help!
  • Allow to save starter kit options as JSON profiles (#5537)

Q4 2022

  • Publish official Quasar Organizational chart
  • Start working on Quasar v3
  • More triaging automation (quasarframework/rfcs#10)
  • 2022 Quasar Survey
  • December 31th 2022 marks the end of life for Quasar v1. It will no longer receive updates. (postponed, originally EOL was 1st of April 2022)

Archive

Q1 2022

  • ✌️ (DONE) First beta of a new CLI for Quasar based on Vite.js instead of Webpack (will have its own life along with the current Webpack-based CLI)
  • ✌️ (DONE) Fix intellisense problem for packages provided by @quasar/app (#9235)
  • ✌️ (DONE) Add automatic tests to Quasar UI (#12047)
  • ✌️ (DONE) Support Pinia out-of-the-box (#12707)

Q4 2021

Q3 2021

Q2 2021

  • ✌️ (DONE) Upgrade the App CLI for Quasar v2 to Webpack v5 (reference)
  • ✌️ (DONE) Quasar v2 will become officially the "latest" version of Quasar. The documentation website (https://quasar.dev) will point to v2 and the v1 docs will live under https://v1.quasar.dev. The end of life for Quasar v1 will be March 2022 and we will keep on backporting fixes and new features from v2 to it until then.