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

vinary

v1.0.17

Published

A small JS library to add Reactivity and Data Streams to your projects

Readme

Vinary: Mini-DOM Library for Vanilla JS lovers

Vine is built to make your html files Reactive with minimalistic syntax. A simple function like this:

createState({
    fname: 'Rishom',
    lname: 'Rozario',
    decription: 'Web-dev enthusiast. I Love React and Angular'
})

...and an HTML file like this:

<h1>{{fname}} {{lname}}</h2>
<p>I am a {{description}}</p>

... is a lot better than the boring old

elem1.textContent = fname + lname
elem2.textContent = 'I am a' + description + description2 + description3 + and_so_on

The createState() can also take a callback.

const callback = (object, property, element) => {
    if (element.nodeName === 'INPUT') {
        element.addEventListener('keydown', (e) => {
            object[property] = e.target.value
        })
    }
}

createState({
    fname: 'Rishom',
    lname: 'Rozario',
    decription: 'Web-dev enthusiast. I Love React and Angular'
}, callback)

Let's break this piece of code down and see what the callback() actually does. The function takes three parameters:

  • The object parameter is an object that is similar to the object in the createState() function. It reacts to all the changes made in the DOM anf the Javascript file.
  • The property is the key of the object, like fname for instance.
  • The element is any element with the 'bind' property set (<h1 bind='description'></h1>), which we will check a bit later, or the part of the HTML within braces ({{description}})

The ' if ' statement checks whether the element is an input field

If the element is indeed an input field, a 'keydown' event is attached that changes the property within the object.

It is important to note that the object whose property is being changed is similar to but not an actual copy of the object in createState(). This means that making changes to the original object does not affect the DOM

Also, the callback is called when parsing the HTML, yes the HTML is parsed during runtime, or, more accurately, when setting the values in the placeholders. It is fired for every element that acts as a placeholder and the property and element parameters are changed every time.