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

@warblerjs/frontend

v0.6.0

Published

Lightweight browser utilities for Warbler applications, built on native Web APIs.

Readme

@warblerjs/frontend

Small, dependency-free browser utilities for Warbler applications. The package stays close to native Web APIs and removes repetitive frontend boilerplate.

bun add @warblerjs/frontend
import { http, csrf, form, storage, debounce } from "@warblerjs/frontend";

const users = await http.get("/api/users");
await http.post("/api/users", { name: "John" });
const data = form.serialize("#login-form");
const token = csrf.token();
storage.set("theme", "dark");

Native forms

import { FormBuilder } from "@warblerjs/frontend/forms";

const login = FormBuilder("login-form", (v) => ({
  email: ["", v.required(), v.email()],
  password: ["", v.required(), v.minLength(8)],
}));

login.value();                 // { email: string, password: string }
login.field("email").value(); // string

FormBuilder discovers controls by native name, applies equivalent HTML constraints, and keeps values, validity, touched/dirty state, accessibility attributes, and data-wbr-* state in sync. Errors render through textContent into [data-wbr-error-for] containers.

A form with an explicit action keeps valid native browser submission. Without action, a valid submission uses Fetch with native FormData; GET/HEAD values are placed in the URL. submitted records attempts while submitting represents only an active fetch. Field server errors clear when that field changes.

destroy() is idempotent. It removes listeners and callbacks owned by the instance, aborts an active submission, restores developer-provided constraints and accessibility attributes, and prevents stale asynchronous work from updating the form. Reinitializing the same native form automatically destroys its previous owner, which makes page-script re-execution and HMR safe.