Download websites that use Vue2-animate

About Vue2-animate

An animation helper is a dependency a project adds early and rarely revisits, which is what makes a small one worth reading closely when it turns up. The library recorded here, published in 2016 under the MIT licence, is a thin bridge between a familiar vocabulary of animation class names and the transition names Vue expects, with CSS recorded on our side as the implementation language.

Nobody reaches for a bridge like that unless a front end is being assembled from components rather than served as finished pages. The project's own page offers these transitions for the second and third major lines of Vue and for Alpine.js, so the package tells you which animation vocabulary a team adopted rather than which generation of the framework it is stuck on. As of October 2026 we detect Vue2-animate on 14 sites.

A dependency signal is commercially interesting in a way an animation helper is not. Agencies pitching front-end work want a list of sites whose interfaces are assembled from components rather than from a page builder. Security teams want the same list for a different reason, because every third-party stylesheet in a build is one more thing to inventory and to keep patched. Vendors of component libraries and hosted front-end platforms use it to see which projects already carry a helper of this shape and what their own products would sit beside.

Detection has a real ceiling here. The library is visible only while its class names survive into the shipped stylesheet, and a build step that purges unused selectors, renames them, or inlines them into a component bundle removes the evidence without removing the dependency. Copies pasted into a project's own stylesheet disappear for the same reason. Our figure is a floor, and a biased one, weighted towards sites that ship plain stylesheets rather than aggressively optimised bundles.

The bias is worth stating because it changes who ends up in the list. Sites with simple builds tend to be smaller, older, or maintained by whoever had time, which is the same population that migration offers and security audits are usually aimed at. The useful move is to join these domains with the framework detections in the same export, since a helper class name plus a framework signature describes a front end far better than either alone. A per-domain check tells you whether one site you already care about carries the pairing. The export is what turns a hunch about a whole segment into a list of names you can act on.