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

merv

v0.0.1

Published

That mustache with that little bit extra

Readme

merv

merv is an opinionated wrapper around the excellent (and minimal) mustache templating library.

NPM

experimental

Why?

IMO, we overcomplicate things for for building simple web applications and sites these days. Surely we can take a solid piece of tech, use some new code idioms (such as async..await) and get some real milege with only a few packages.

Usage

Basically, merv expects a certain convention. For things to work swimmingly the following directory structure is advised:

- templates
  |- a.html
  |- b.html
- partials
  |- x.html
  |- y.html
- layout.html

(Both the layout.html file and partials directory are optional.)

Here's a quick look at what a template file might look like:

<html>
  <head>
    <title>{{title}}</title>
    {{> partial:meta }}
  </head>
  <body>{{> main}}</body>
</html>

You can see we are using the standard mustache partial syntax but we are managing the partial loading ourselves. This might seem a little contrived, however, the advanced usage is coming soon.

With things set up like this you can then do something like the following:

const { loadTemplates } = require('../../');

// initialise merge with details of the path
async function main() {
  const { render } = await loadTemplates({ templatePath: __dirname });
  const data = { title: 'foo' };
  console.log(render('a'));
}

main();

What is happening here is that we have told merv that we want to render the a template. So diligent merv does that first, but then goes the extra mile to see if we have a layout.html file around. If so it then uses the {{> main}} partial to inject the output of the originally requested template into the appropriate position.

Approach

While mustache has a limited set of features, it has enough in it's toolkit to everything you are going to need. While I'd commonly got to a more heavy weight templating engine such as PUG for layouts, includes of abritrary file content; these are all things that can be achieved with mustache.

Merv is just a collection of the general patterns that I have found to work to perform some of these tasks.

Limitations

This is designed for server side rendering only. Really it has no designs on being anything useful for the client-side. You should reach for those tools that are geared towards client rendering in those cases.

What's with the name?

See: https://en.wikipedia.org/wiki/Merv_Hughes

LICENSE

The MIT License (MIT)

Copyright (c) 2019 Damon Oehlman [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.