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

ren

v0.3.1

Published

Declarative view rendering.

Readme

Ren

Declarative, streaming HTML renderer.

API

var ren = new (require('ren'))(options); // More about options below
var data = {
  template: 'views/page.hbs',
  data: {
    '#navbar': {
      template: 'views/partials/navbar.hbs',
      data: {
        links: {
          foobar: '/foobar',
          bar: '/baz/foorad'
        }
      }
    },
    '#contents': {
      template: 'views/page_content.hbs',
      data: {
        title: 'this is my page',
        introduction: 'lorem ipsum dolor sit amet',
        aListOfStuff: ['a', 'b', 'c', 'd'],
        // Prefix denotes a subview
        '#anotherTemplate': {
          template: 'views/foobar.hbs',
          data: {
            foobar: 'baz'
          }
        }
      }
    }
  }
};

server.on('request', function (req, res) {
  ren.render(data).pipe(res);
});

How it works

  • Analyses view hierarchy and creates a render queue.
  • Each "parent" template gets it's child templates as dependencies set up
  • Once each child view is rendered the parent is put on the render queue
  • Rendered from leaf-nodes back to root node

Data altering

Before each view is rendered the willRender event is emitted with the RenderNode passed as data to the event listener. You can use this event to modify data or template in a node before it's actually rendered.

You can use this to inject additional data, transform it or whatever.

Options

  • basePath, the base path used for view loading. Defaults to cwd.
  • concurrent, number of views to concurrently render. Defaults to 2.
  • prefix, change the prefix that denotes subvies. Defaults to #.
  • defaultCompiler, set to extension of your default view format. You can then omit the extension in your template properties. Defaults to .hbs.
  • disableCache, loads each view every time it is rendered. Useful during dev. Defaults to false.
  • compilers, an object where the keys are extensions and the values are a function that compiles a template (ie. Handlebars.compile). REQUIRED.

License

MIT