New major version for q/app-vite (v3)

[rstoenescu]

Update 8th May, 2026

• Added support for PNPM v11
• Docs update for q/app-vite v3 are under way (almost ready)
• create-quasar updated for q/app-vite v3 project folders (not released yet)
• create-quasar will have option for oxlint + oxfmt (along with current ESLint)

Original announcement

Hi everyone!

We've been working hard on the next major version of @quasar/app-vite (v3), and development is in its final stages before the public beta. The improvements are massive. We've focused heavily on modernizing the CLI to make it cutting-edge and much easier to use.

Barring any unforeseen issues, we expect to release it in 2-3 weeks (or even sooner if the stars align correctly!).

Here is a bird's-eye view of what to expect:

• ⚡ Blazing Fast Compilation: We've replaced esbuild with Rolldown for /src-* folders and completely redesigned the build architecture. Build steps are now parallelized across all Quasar modes, resulting in significantly faster speeds and a smaller footprint for your production distributables.

• ⚙️ Next-Gen Environment Management: We’ve redesigned env file management from the ground up. You will no longer need to restart the dev server when making changes to these files, and you can now use them directly within your quasar.config file too!

• 🔒 Enhanced Security & Modern Standards: We’ve migrated from process.env to the modern import.meta.env (aligning with Vite's native model) with full TypeScript support. A new security layer ensures client-side files only use a configurable prefix for env definitions, preventing potential leaks of sensitive data.

• 📦 Smarter Dependency Isolation: We now have a clear separation of dependencies for each Quasar mode. You can install mode-specific packages directly in their respective /src-* folders. For example, the default Electron app will no longer require dependencies to be installed in its dist folder—only what you explicitly install in /src-electron will be included.

• 🌍 Redesigned SSR Architecture: SSR mode now features superior support for custom web servers and proper TypeScript integration. When adding SSR, the CLI will prompt you to spawn a preconfigured /src-ssr folder using Hono, Fastify, Express, or Koa (let us know what other out-of-the-box servers you’d like!).

• 📂 New Server Assets Folder for SSR: We've introduced a /src-ssr/server-assets folder alongside helpful utility functions. This makes it incredibly easy to reference assets (like HTTPS certificates) across dev and production runtimes, eliminating the strict need for an Apache/Nginx wrapper. We've also made the serverless support a breeze.

• 🚀 Paving the Way for SSG: This new SSR architecture lays the necessary groundwork for us to finally release Static Site Generation (SSG) mode in the future.

• 🖥️ Revamped Electron Mode: We’ve added lots of new features to make desktop development smoother. Similar to SSR, we've introduced a /src-electron/electron-assets folder. Referencing files from here (or from the /public folder) is now much easier via new utility methods available in both /src-electron and /src.

• 🛠️ Modernized Core: The codebase has been updated to take full advantage of Node.js v22+ features, alongside countless other small but significant improvements across all Quasar modes to boost your productivity.

This is just a high-level overview of what @quasar/app-vite v3 brings to the table. There are many more quality-of-life updates that add up and will definitely increase your productivity.

Relevant updates will be posted on this thread as we make progress. Stay tuned!

Finally, a quick favor to ask: Please consider supporting our efforts! If you use Quasar at work, drop a message to your management about sponsoring us at https://donate.quasar.dev/. We rely on your support to make massive updates like this possible!

[zanzara]

Nice outlook. Indeed.
Regarding SSR: I would have definitely an eye on defineSsrMiddleware when choosing something different as express.
Often apps runs behind a Traefik Reverse Proxy and then some special settings can be crucial.
So as long an alternative server to express is listed here:
https://github.com/chimurai/http-proxy-middleware#compatible-servers
it's Ok.

[Rolanddoda]

For Quasar v3, I would propose:

• First class support for Tailwind CSS
• Enhance support for custom styling. Pair that with Tailwind, you just need to allow setting classes for elements, just like Nuxt UI, PrimeVue, etc do where they have a prop to add classes.
• Unstyled components (Nowadays, every UI framework should have that)
• Ability to use Quasar only as a UI framework, meaning enabling SSR and things that prevent it to be used with Nuxt

[rstoenescu]

Hi,

This is not about Quasar UI v3. It's about the version 3 of Quasar CLI with Vite (@quasar/app-vite package).
We will make a separate announcement for Quasar UI v3.

Ability to use Quasar only as a UI framework, meaning enabling SSR and things that prevent it to be used with Nuxt

There is infinite possible complexity of how SSR runs. While Quasar UI can work in SSR (obviously, we do have SSR mode with q/app-vite), we try to do our best to simplify the usage, avoid boilerplate, and offer many features out of the box without you, the devs, having to reinvent the wheel. There are scenarios where making such features work with any SSR CLI would mean increasing the boilerplating for everyone while having huge headaches. Some features are not even possible and we'd need to PR external tools for them. However, we will be thinking hard about how we can improve all this for Quasar UI v3.

[rstoenescu]

Update 8th May, 2026

• Added support for PNPM v11
• Docs update for q/app-vite v3 are under way (almost ready)
• create-quasar updated for q/app-vite v3 project folders (not released yet)
• create-quasar will have option for oxlint + oxfmt (along with current ESLint)