Download websites that use Quasar

About Quasar

Quasar exists to solve a problem that has nothing to do with websites. A team writes one Vue codebase and ships it as a web application, an installable progressive web app, a mobile binary and a desktop build. Only the web target is visible to a crawler, so a census of sites is by construction a partial view of where the framework is used. Anyone comparing the count below against community size, package downloads or job postings should expect the figures to disagree, and the disagreement is not an error in any of them.

Within the target we can see, presence is informative. Sites built on a component framework of this kind are applications rather than pages. Dashboards, booking flows, internal tools with a public login, portals, configurators. Marketing sites rarely need one and rarely carry one. So the population skews toward products with a signed in state behind the front door, a segment that ordinary content classification never isolates cleanly.

The engineering profile behind the detection is consistent. A team using Quasar has committed to Vue, works in JavaScript across the whole stack, and often chose the framework precisely because a single codebase had to reach further than the browser. Recruiters, component vendors, testing and monitoring providers, and anyone selling into front end teams want that population rather than the general web. The framework is MIT licensed and dates from 2016, so the install base has had long enough to accumulate production systems rather than experiments.

As of September 2026 we detect Quasar on 1,457 sites in the JavaScript frameworks bucket. A per domain lookup confirms a single application. The export answers the questions that need the whole set, such as which industries adopted a multi target Vue stack, which backends and payment providers appear alongside it, and how the population trends between releases of the file.

Detection deserves a caveat of its own. Compiled front end bundles are minified and hashed, and identification depends on artefacts that survive the build, such as class name conventions, component markup and asset naming. A custom build configuration, aggressive tree shaking or a rename can erase them, and a server rendered page hands over less evidence than a client rendered one. The recorded count is conservative, and it grows more conservative as build tooling gets better at hiding what produced the output.