Download websites that use petite-vue

About petite-vue

Every so often a front end tool arrives whose selling point is how little of it there is. petite-vue is a stripped down subset of Vue, meant to be dropped into a server rendered page with a script tag and used for the small interactive parts: a dropdown, a filter, a tab strip, a form that validates before it submits. Nothing about the library is intended to grow into an application.

The design choice tells you what kind of site you are looking at. A team that reaches for a minimal reactive layer has usually decided, deliberately, not to build a single page application. Pages come rendered from a backend, the markup arrives complete, and the scripting exists to make a few components respond. Finding petite-vue on a domain is therefore a fairly reliable marker of a server rendered architecture paired with a modern front end sensibility, a combination that coarse framework detection normally cannot separate.

Age and version data support the same reading. The project appeared in 2021 under an MIT licence, written in JavaScript, and we have recorded only 2 distinct versions in the wild, 0.4.1 among them. A library with a version list that short is either very new or effectively finished, and this one reads as finished: small, stable and deliberately unambitious, with no release cycle to speak of. Sites do not upgrade the library because there is nothing to upgrade to.

As of September 2026 we find it on 2,486 sites, which places it among the smaller entries in the Miscellaneous category. Small is the correct expectation here. A library distributed mainly by script tag and adopted by developers who read release notes will never spread the way a bundled framework default does, and the population it does reach is unusually self selected. A site on this list was built by somebody who made a considered choice, which is a rarer and more informative signal than a framework that arrived inside a purchased template.

Detection carries the limit every client side library carries. Code that is bundled and minified into one application file loses the markers we match on, so what we observe skews towards the script tag usage the library was designed for and misses installs that went through a build step. For anyone tracking front end adoption, developer tooling, or the slow drift away from heavyweight architectures, the value sits in the whole file rather than in any single row: which domains, on which top level domains, beside which other technologies, and how the set grows between one export and the next.