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

@phibre/neta

v0.0.5

Published

A lightweight JS framework powered by the prototype chain.

Readme

Introduction

neta ネタ — Japanese for the topping of sushi, usually the fish part of nigiri, provides a JS-only framework for the modern web. Where other frameworks rely on some special markup language, like JSX, neta provides a simple and easy to use API in plain Javascript. No compilation needed!

Getting Started

Coming soon...

Composition

To tell neta how to render a DOM-Element, you provide it with something called a descriptor, which is just a fancy word for an object containing all information about the desired Element. This object will then extend the previously defined descriptor. This way we can add certain properties like styling, attributes, children, etc. on one element and override, mix or extend them in another.

Note: neta relies on the prototype chain to extend partials. This means, property lookups are handled by the browser 🎉

Simple element creation:

neta.document({
    body: html({ text: 'Hello World!' })
});

You can partially apply a descriptor and reuse it:

const div = html({ tag: 'div' });
const red = html({ styles: { color: 'red' } });

neta.document({
    body: div(red)({
        children: [
            div({ text: 'Hello World!' }),
        ],
    }),
});

Components

To abstract certain functionalities you can wrap your descriptor in a function. This allows you to map the properties or make invocations only when you actually need them.

function icon({ url }) {
    // Do something here
    return html({
        tag: 'img',
        attributes: {
            src: url,
        },
        styles: {
            width: '100%',
        },
    });
}

neta.document({
    body: html({
        children: [
            icon({
                url: 'https://picsum.photos/200/300',
            }),
        ],
    }),
});
app.mount(parent);

Reactivity

To let neta keep track of changes you can pass it an observable instead of any attribute, style or child. An observable can be a Promise, a value wrapped in the provided state function, or anything that implements a then function similar to a Promise really.

const time = state();

setInterval(() => {
    time.set(new Date().toLocaleTimeString());
}, 1000);

neta.document({
    body: html({ text: time }),
});

Styling

Hooks

Helpers