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/behavior

v1.1.23

Published

Framework-free behavior for Mlola UI markup: standard DOM, no runtime peers

Readme

@mlola-ui/behavior

Framework-free interaction behavior for Mlola UI markup. Standard DOM only: no framework, no build step, no runtime peers, and no renderer of its own. Mark a root with data-ml="<behavior>" and enhance it, or call observe() once and let new markup enhance itself.

The decisions themselves — which index a key moves to, where focus goes, what a value snaps to — live in @mlola-ui/behavior/logic as pure functions, so React components and this runtime cannot drift apart.

Install

npm install @mlola-ui/behavior

Use

<link rel="stylesheet" href="@mlola-ui/engine" />

<div data-theme="atelier" data-mode="light">
  <div data-ml="tabs">…</div>
</div>

<script type="module">
  import { observe } from "@mlola-ui/behavior";
  observe();
</script>

It is idempotent, so it is safe to call after a framework re-render, a turbo navigation, or an htmx swap.

Examples

examples/ holds the markup for each behavior, one file per behavior, as it should be written by hand. They are the markup the browser suite runs in Chromium, Firefox and WebKit, and the markup the component docs show.

Implemented behaviors

accordion, tabs, dropdown-menu, select, modal, sheet, tooltip, toast, switch, slider — the same list the engine's behavior-spec.mjs specifies, checked by the contract audit.

Exports

| Path | What it is | | --- | --- | | @mlola-ui/behavior | enhance, observe, destroy, behaviors | | @mlola-ui/behavior/logic | pure decisions shared with React |

MIT licensed. Part of Mlola UI.