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 🙏

© 2025 – Pkg Stats / Ryan Hefner

schema.engine

v1.0.3

Published

schema oriented DOM rendering engine

Readme

Schema Engine

Schema is a front-end library for rendering object-literal components to the DOM. Object-literal components act as schemas that describe the HTML, CSS and JS that the component encapsulates.

A component is simply an object literal, acting like a schematic for the DOM structure it describes.

const Button = {
  data: { label: 'Submit' },
  template: ['button', '.btn', '!onclick: submit', '@label'],
  styles: {
    '.btn': {
      color: '#333',
      padding: '10px'
    }
  },
  submit: (self) => {
    self.setData({ label: 'Submitted' });
    self.setStyles({ '.btn': { color: '#ddd' } });
  }
}

To render a component just pass it into the SchemaEngine, along with the element to mount it to.

  const engine = new SchemaEngine;
  engine.render(Button, document.getElementById('root'));

What's with the template structure? It is just an array, or an array of arrays if there's nesting.

  ['div', '.divClass', 'This is the content of the div']

Will be generated directly in the DOM, but the HTML representation would look like:

  <div class='divClass'>This is the content of the div</div>

Some sugar can come into use.

  ['.divClass', 'This is the content of the div']

Some nesting.

  ['.divClass',
    ['.childDiv', 'This is a child div']
  ]

The first string in the array is always a tag (id or class for divs). The last string is always the content of the tag. Everything between are attributes.

  ['.divClass', '#parentClass', 'data-id: p1',
    ['a', 'href: https://github.com', 'Github'],
    ['img', 'src: images/icon.png', '']
  ]