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

@mlola-ui/engine

v1.13.2

Published

Framework-free CSS, spring easings, and the machine-readable contract for Mlola UI

Readme

@mlola-ui/engine

Generated CSS and machine-readable metadata for Mlola UI. Framework-free: it emits plain CSS and JSON, so it runs with React, plain HTML, Rails, Go, or a static file, and has no runtime dependency.

The engine is the reason a model cannot hallucinate this library. Its contract.json is derived from the stylesheet itself and lists every class and the data-* / aria-* attributes the CSS reacts to, and agents.md is generated from the same source. An assistant reading them cannot invent a class that does not exist.

Install

npm install @mlola-ui/engine

Use

@import "@mlola-ui/engine";
<html data-theme="atelier" data-mode="light">
  <button class="ml-button" data-variant="primary">Save</button>
</html>

Exports

| Path | What it is | | --- | --- | | @mlola-ui/engine | the ordered cascade: tokens, foundations, materials, recipes, motion | | @mlola-ui/engine/tokens.css | theme + semantic tokens, light and dark | | @mlola-ui/engine/recipes.css | component recipes | | @mlola-ui/engine/motion.css | keyframes, spring easings, reduced-motion collapse | | @mlola-ui/engine/contract.json | every class and the attributes it reacts to | | @mlola-ui/engine/tokens.json | DTCG token document |

Build

The engine is generated by a Node 20 script, so the output is reproducible:

node build.mjs
node build.mjs --check   # fails when generated output is stale

MIT licensed. Part of Mlola UI.