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

svenjs

v3.4.0

Published

A tiny UI runtime. One HTML file, a button, state. No npm required.

Readme

SvenJS 3

A tiny JavaScript framework for composable web apps. JSX, immutable state, keyed DOM patch. No compiler.

Save as hello.html and open it. No npm.

<script src="https://unpkg.com/svenjs@3"></script>
<div id="app"></div>
<script>
  const { create, render, html } = Svenjs;
  const App = create({
    initialState: { clicks: 0 },
    render() {
      return html`
        <button onClick=${() => this.setState({ clicks: this.state.clicks + 1 })}>
          ${this.state.clicks}
        </button>
      `;
    },
  });
  render(App, document.getElementById("app"));
</script>

With a bundler: npm install svenjs, then JSX via "jsxImportSource": "svenjs".

Production files omit development checks. Bundlers that honor the "development" export condition load svenjs.dev.js automatically. A script tag that wants warnings should use svenjs.iife.dev.js; NODE_ENV=development cannot restore code already removed from the production build.

For static HTML, render the same tree on both sides and hydrate it in the browser:

import { hydrate, renderToString } from "svenjs";

// build/server
const markup = renderToString(<App url="/docs" />);

// browser
hydrate(<App url={location.pathname} />, document.getElementById("app"));

initialState accepts a value or (props) => state. In development, state is cloned and deep-frozen; non-cloneable values fail clearly instead of being silently discarded. Production assigns the next value. this.observe(store) re-renders when a store changes.

This is a rewrite of 2.x. Not drop-in compatible (svenjsx-loader is gone; setState still replaces, does not merge).

ISC license.