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

@dotlabel/temple

v1.3.0

Published

Creates files from templates

Readme

Temple

Super simple utility to scaffold templated files

Example

temple render readme.hjs > README.md

Temple will pull templates from its storage and use data from your package.json to output a rendered file.

Installation

npm i -g @dotlabel/temple

## Usage

Temple is self-documenting as much as possible, use --help to get additional information about Temple and each command.

temple --help
temple render --help

Temple needs only a couple of things to work

  • A template engine specification
  • Some templates

Specifying and installing templating engines

Temple uses consolidate to render templates and will not install engines unless instructed to do so.

A template engine specification consists of three fields that you need to consider:

{
  "name": "hogan",
  "module": "hogan.js",
  "extensions": [
    "hjs",
    "hogan"
  ]
}
  • name the identifier shared with consolidate
  • module the module name to install from npm when required
  • extensions Temple will attempt to match template file extensions to those listed by the engine specification i.e. readme.hjs would imply using hogan to render the template.

The easiest way to register a template is to stream in a specification

echo '{"module":"hogan.js","extensions":["hjs"]}' | temple engine hogan

There are a few other options, see temple engine --help.

Once the specification is loaded then you’re free to install it, although Temple will prompt you if you forget this step and try to use a template file requiring the engine.

temple engine --install hogan

Specifying a template file

Easiest way is to stream the template file in.

echo '# {{ name }}' | temple register readme.hjs

See temple register --help

Rendering a template file

Once you have a few templates and at least one engine registered with Temple you’re set to get going

temple render readme.hjs > README.md

In these examples we have registered hogan as a templating engine and added a readme.hjs template file, when we attempt to render it Temple checks the extensions, finds that it matches hogan and uses hogan.js to render the template to stdout, additionally prompting to install hogan.js if necessary.

License

MIT