npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@oglofus/tailwind-viewport-animations

v1.0.1

Published

Viewport animation utilities for Tailwind CSS v4

Readme

@oglofus/tailwind-viewport-animations NPM Version Publish Package to NPM

Viewport animation utilities for Tailwind CSS v4.

Demo: https://oglofus.github.io/tailwind-viewport-animations/

Install

npm install @oglofus/tailwind-viewport-animations

Tailwind v4 usage (plugin)

In your main stylesheet:

@import "tailwindcss";
@plugin "@oglofus/tailwind-viewport-animations";

Then use classes in your markup:

<section class="va va-slide-up va-start-15 va-end-75">...</section>

Included utilities

  • va
  • va-start-{number} -> number is treated as % (va-start-23 => 23%)
  • va-end-{number} -> number is treated as % (va-end-23 => 23%)
  • va-start-[...] arbitrary value (va-start-[80%], va-start-[12rem])
  • va-end-[...] arbitrary value (va-end-[20px], va-end-[var(--my-range)])
  • va-fade
  • va-zoom
  • va-slide-left
  • va-slide-right
  • va-slide-up
  • va-slide-down
  • va-blur-in
  • va-rotate-in
  • va-pop
  • va-reveal-up
  • va-flip-y
  • va-duration-{number} -> milliseconds (va-duration-800 => 800ms)
  • va-duration-[...] arbitrary duration (va-duration-[1.4s])
  • va-distance-{number} -> pixels (va-distance-120 => 120px)
  • va-distance-[...] arbitrary distance (va-distance-[20vh])
  • va-ease-linear
  • va-ease-in
  • va-ease-out
  • va-ease-in-out
  • va-ease-smooth
  • va-ease-snap
  • va-ease-[...] arbitrary easing (va-ease-[cubic-bezier(0.17,0.67,0.83,0.67)])
  • va-once
  • va-repeat
  • va-group-[name] exposes a named timeline scope on a parent container
  • va-subject-[name] names an element as a view timeline subject
  • va-target-[name] names an element as its own view timeline subject and targets that named timeline

Timeline names use arbitrary values, for example va-group-[cards] or va-target-[--cards]. Bare names are automatically prefixed to CSS timeline identifiers (cards -> --va-cards).

Example combos

<div
  class="va va-reveal-up va-start-[80%] va-end-[20px] va-distance-160 va-duration-700 va-ease-smooth"
></div>
<div
  class="va va-flip-y va-start-23 va-end-65 va-duration-[1.2s] va-ease-[cubic-bezier(0.2,0.9,0.2,1)]"
></div>

Named container targets

Use va-group-[name] on a scrollable ancestor to expose a named timeline scope inside that container.

Same element as subject and target

Use va-target-[name] on the animated element when the element should animate against its own visibility inside the named scroll area:

<div class="max-h-96 overflow-y-auto va-group-[cards]">
  <article class="va va-slide-up va-target-[cards] va-start-50 va-end-80">
    ...
  </article>
</div>

This is the closest equivalent to a Tailwind group-* style API for non-window scrollers.

Separate subject and target

If one element's visibility should drive a different element's animation, split the subject and target:

<div class="max-h-96 overflow-y-auto va-group-[cards]">
  <div class="va-subject-[cards]">Tracked subject</div>
  <div class="va va-fade va-target-[cards]">Animated target</div>
</div>

Utility roles

  • va-group-[name] sets timeline-scope on a shared ancestor
  • va-subject-[name] names an element as a view timeline subject
  • va-target-[name] points .va at that named timeline and also names the element as a subject for the common same-element case

These named utilities still use CSS view timelines, so the tracked scroller is the subject element's nearest ancestor scroll container. In practice, that means the scrollable parent should usually have overflow-y-auto or overflow-y-scroll.

Browser support note

These utilities rely on animation-timeline: view() / scroll-driven animations. Ensure target browsers support this API.

Compatibility reference: https://caniuse.com/?search=animation-timeline

Used by

  • https://deskify.app
  • https://oglofus.com
  • https://uploft.app