Quasar Framework - Build high-performance VueJS user interfaces in record time
27.2k
Stars
3.7k
Forks
662
Open issues
30
Contributors
AI Analysis
Quasar Framework is a Vue.js-based UI framework for building responsive single-page applications, server-side-rendered apps, PWAs, browser extensions, hybrid mobile apps, and Electron desktop applications from a shared codebase. It serves developers who need rapid multi-platform deployment with Material Design components and targets teams building consumer-facing web and mobile applications at scale.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Quasar Framework: Vue.js all-in-one toolkit for SPA, SSR, PWA, mobile, and desktop from a single codebase
Quasar is a mature Vue.js-based UI framework that lets developers build multiple deployment targets — single-page apps, server-side rendered apps, PWAs, browser extensions, Electron desktop apps, and hybrid mobile apps — from one shared codebase. It bundles a comprehensive Material Design component library with its own CLI and build tooling. Its target audience is Vue.js developers who want to ship cross-platform applications without stitching together multiple separate tools. With 10+ years of development and active sponsorship, it occupies a stable position in the Vue ecosystem.
Founded in 2015 by Razvan Stoenescu, Quasar predates many modern Vue tooling options. It migrated from its own webpack-based CLI to Vite-based tooling and added TypeScript support as the Vue 3 ecosystem matured.
Quasar grew steadily through 2018–2022 as Vue.js adoption expanded globally and developers sought all-in-one solutions. Growth has plateaued relative to the broader Vue ecosystem as Nuxt matured and component libraries like Vuetify gained parity in cross-platform scope. Recent star velocity (4 stars/week) suggests a stable but slowly growing or flat adoption curve rather than accelerating momentum.
The sponsor list includes named commercial entities (iRewind, Qintil, Kalisio, Certible, Acorn Finance, etc.), suggesting real business usage. The quasar-awesome community showcase exists publicly. NPM download data is not included in available metadata, but 27K+ stars and a decade of releases make it likely that meaningful production usage exists across small-to-medium enterprise Vue projects globally.
Appears to follow a monorepo structure with separate packages: the core UI library (quasar), CLI tools (@quasar/cli, @quasar/app-vite), a Vite plugin (@quasar/vite-plugin), icon utilities (@quasar/icongenie), and extras (@quasar/extras). The framework likely abstracts platform-specific build configurations behind a unified CLI layer, with Vite as the primary bundler for current versions.
Not documented in README. CI badges reference a 'build-types' workflow, suggesting TypeScript type correctness is validated in CI, but broader test coverage metrics are not exposed.
Last push was 2026-06-17, four days before the evaluation date, indicating active maintenance. The project has been continuously developed for over a decade. Sponsored by multiple companies including DigitalOcean and BairesDev, suggesting financial sustainability. The monorepo structure and versioned sub-packages imply disciplined release management.
ADOPT IF: you are a Vue.js team that needs to target multiple platforms (web SPA, SSR, PWA, desktop, mobile) from one codebase and value opinionated, integrated tooling over composing a custom stack. AVOID IF: you are building a web-only application (Nuxt is likely a better fit), need the absolute latest ecosystem integrations, or require highly customized build pipelines that conflict with Quasar's CLI opinions. MONITOR IF: you are evaluating long-term Vue ecosystem strategy — Quasar's growth trajectory is flat relative to Nuxt and the broader ecosystem, and it's worth watching whether the project sustains its cross-platform differentiation as Nuxt expands its own target coverage.
Independent dimensions
Mainstream potential
4/10
Technical importance
7/10
Adoption evidence
6/10
- Flat star growth and low recent velocity (4 stars/week) suggest the project may be losing mindshare to Nuxt and component-library-agnostic approaches, which could affect long-term community size and third-party plugin availability.
- Heavy framework opinions and custom CLI tooling create lock-in: migrating away from Quasar once a project is established is non-trivial, especially if Electron or Capacitor integrations are used.
- The project appears dependent on a small core team and a limited number of commercial sponsors; loss of key maintainers or sponsors could affect long-term sustainability, though this risk is partially mitigated by 10+ years of continuity.
- TypeScript support and type safety appear to be improving (build-types CI) but the primary language remains JavaScript, which may deter teams standardizing on TypeScript-first frameworks.
- Cross-platform 'write once, deploy anywhere' promises often encounter platform-specific edge cases in production; Quasar abstracts these but developers may still face undocumented integration friction with native mobile or Electron-specific APIs.
Quasar will likely retain a loyal but slowly shrinking relative share of the Vue ecosystem as Nuxt and lighter composable stacks continue to attract new Vue developers. Its cross-platform story remains its clearest differentiator.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://quasar.dev
- Language
- JavaScript
- License
- MIT
- Last updated
- 1d ago
- Created
- 131mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
quasarframework/quasar
this
|
27.2k | +6 | JavaScript | 8/10 | 1d ago |
 vuejs/core
|
53.9k | — | TypeScript | 9/10 | 8h ago |
 vuetifyjs/vuetify
|
41k | — | TypeScript | 8/10 | 2d ago |
 QwikDev/qwik
|
22k | — | TypeScript | 8/10 | 19h ago |
 nuxt/nuxt
|
60.6k | — | TypeScript | 9/10 | 16h ago |
 youzan/vant
|
24.3k | — | TypeScript | 9/10 | 3d ago |
Vuetify is purely a Vue UI component library (Material Design) without built-in cross-platform deployment targets. Quasar adds CLI, build targets (Electron, Capacitor, SSR, PWA), and opinionated project structure on top of a comparable component set. Vuetify has more GitHub stars and may have wider adoption as a component-only dependency.
Nuxt focuses on SSR/SSG/hybrid rendering for Vue web apps and has significantly more momentum (60K+ stars). Quasar covers more deployment targets (mobile, desktop) but Nuxt's module ecosystem and meta-framework positioning make it a stronger choice for web-only Vue SSR applications.
Ionic with Vue offers a similar cross-platform story (web + mobile), with stronger native mobile integration via Capacitor. Quasar bundles more into a single framework, while Ionic is more modular. Teams needing deep native mobile features may prefer Ionic's toolchain.
Developers can assemble their own Vue stack with Vite, a component library, and deployment-specific tools. This gives more control but requires more setup and maintenance. Quasar trades flexibility for integrated convenience — a valid tradeoff for smaller teams or speed-to-ship priorities.
For desktop apps specifically, Tauri has become a strong alternative with better performance and smaller binary sizes. Quasar's Electron integration is convenient within its ecosystem but doesn't offer the Rust-based advantages Tauri provides. Teams targeting desktop primarily may evaluate Tauri separately.
