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

motionlil

v0.1.4

Published

A dependency-free Motion DOM runtime compiled with LilScript.

Readme

motionlil

Motion’s browser animation API, ported to LilScript and published as the dependency-free motionlil package.

16/16 paired browser demos ship smaller after Brotli: 12.4% smaller in total, 13.2% median, and up to 23.1% smaller. The installed runtime footprint is 91.0% smaller (11.1× less disk).

| Reproducible result | Motion | LilScript / motionlil | Ratio | Reduction | | --- | ---: | ---: | ---: | ---: | | 16 matching browser demos, Brotli total | 287,404 B | 251,703 B | 0.876× | 12.42% | | Median paired demo, Brotli | — | — | 0.868× | 13.18% | | Best paired demo (perf-stagger), Brotli | 3,844 B | 2,956 B | 0.769× | 23.10% | | Installed runtime | 9,141,537 B | 824,992 B | 0.090× | 90.98% |

The browser figures are matching closed-world builds from the 16-case LilScript Motion lab—not a comparison between unmatched entry points. Every case, its exact ratio, and a live recreation using this package are on the motionlil demo lab.

npm install motionlil
import { animate, motionValue, spring, stagger } from "motionlil"

animate(".card", { opacity: [0, 1], y: [20, 0] }, {
  delay: stagger(0.06),
  duration: 0.35,
})

const progress = motionValue(0)
const unsubscribe = progress.on("change", console.log)
progress.set(0.5)
unsubscribe()

const easing = spring({ stiffness: 300, damping: 24 })
console.log(easing.next(16))

Compatibility

motionlil is built for Vite, Astro, and other ESM bundlers. The default entry is a tree-shakeable JS barrel over separately compiled features (animate, animateMini, scroll, gestures, inView, resize). import { animateMini } from "motionlil" loads only the WAAPI mini runtime. Unused projection / view-transition / visual-element internals are not part of the module graph.

The complete Motion 13 DOM ABI, including constructor and layout internals, stays on motionlil/full.

React-specific entry points such as motion/react are intentionally not included. Use the normal motion package if you need Motion’s React components and hooks.

Available entry points:

import { animate } from "motionlil"       // bundler-facing JS/DOM API
import { animate } from "motionlil/dom"   // same as the default entry
import { animate } from "motionlil/full"  // complete Motion DOM ABI
import { animate } from "motionlil/mini"  // animate + animateSequence
import { recordStats } from "motionlil/debug"

CommonJS and a browser global are also built:

const { animate } = require("motionlil")
<script src="https://unpkg.com/motionlil/dist/motionlil.global.js"></script>
<script>
  motionlil.animate(".box", { x: 100 })
</script>

Vite needs no plugin or configuration:

// vite.config.js is optional
import { animate } from "motionlil"

What “smaller” means

motionlil has no runtime dependencies and publishes only compiled ESM, CommonJS, global builds, and declarations. With Motion 13.1.0 installed in this repository, npm run test:size measures:

| Installed runtime | Unpacked bytes | | --- | ---: | | motionlil npm tarball | 824,992 | | motion dependency tree | 9,141,537 |

That is a 90.98% smaller installed runtime footprint, or 11.08× less disk. The comparison includes motion, framer-motion, motion-dom, motion-utils, and tslib, which npm installs for the upstream package.

The default motionlil ESM entry is a named-export barrel. Vite keeps only the feature files you import. motionlil/full is the complete Motion DOM ABI. Closed-world LilScript app builds can still go further by compiling a concrete program. Run npm run test:size to reproduce the package measurements; the paired demo evidence and methodology are linked from the live lab.

Build pipeline

The LilScript compiler performs whole-program optimization with identifier and property mangling enabled. Each consumer feature is compiled on its own, then published as a separate ESM file so bundlers can drop unused features. CommonJS and the browser global remain single-file builds. Terser runs three compression passes, top-level identifier mangling, and private-property mangling. A second Terser pass, a Vite consumer build, and a named-import shake test are part of the test suite.

To build from source, keep motionlil next to a LilScript checkout, or point to its release compiler explicitly:

npm ci
MOTIONLIL_LILSCRIPT_BIN=/path/to/lilscript npm run build
npm run check

Set MOTIONLIL_BUILD_MODE=development for a faster local build. Production is the default.

Verification

npm test          # Node, ESM/CJS parity, Vite, Terser, export parity
npm run check     # tests, TypeScript declarations, npm tarball audit
npm run test:size # reproducible size report
npm run build:site # build the GitHub Pages demo lab

The implementation is MIT licensed. See NOTICE.md for upstream attribution.