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

templar

v0.2.2

Published

A lightweight template thing

Readme

templar

A minimal template thing for node.js web sites to use.

Works with any template engine that works with Express.

Automatically sends ETags based on the data and the template being used, and 304 responses based on the If-None-Match request header, if the user would be getting the same exact response as last time.

Example

var ejs = require('ejs')
, Templar = require('templar')
, templarOptions = { engine: ejs, folder: './templates' }

// preload it.  Otherwise, the first request is slow, because
// it has to load up all the templates within it.
Templar.loadFolder('./templates')

http.createServer(function (req, res) {
  // note that this causes a sync fs hit the first time if
  // the folder has not been loaded yet.
  res.template = Templar(req, res, templarOptions)

  // .. later, after figuring out which template to use ..
  res.template('foo.ejs', { some: 'data', for: [ 'the', 'template'] })
  //alternatively, you can add a boolean parameter to write to the response without ending it
  //res.template('foo.ejs', { some: 'data', for: [ 'the', 'template'] }, false)
  //just make sure you call res.end() on your own somewhere after that

}).listen(PORT)

Options

  • engine: The engine to use. EJS and Jade both work.
  • folder: The folder where template files are found.
  • cache: Boolean. Set to false to suppress 304 responses and re-read templates without restarting the process.

Partials

Every template will be provided with a local function include(file, data). This function will include another template via a relative path, run it using the data provided, and return the string.

Note that this does not automatically dump the data into the calling template! It's still the caller's responsibility to actually print out the result.

Example

If the template full.ejs contains this:

<!doctype html ALL UP IN YOUR FACE>
<html>
<head><title>yoyoyoyo</title>
<body>
<%- include("partial.ejs", { partial: 1 }) %>
<%- include("partial.ejs", { partial: 2 }) %>
<%- include("partial.ejs", { partial: 3 }) %>
<%- include("partial.ejs", { partial: 4 }) %>
<%- include("partial.ejs", { partial: 5 }) %>
</body></html>

Then, in the same folder, you had a partial.ejs that contained:

<p>is for <%= partial %>

then the resulting output would be:

<!doctype html ALL UP IN YOUR FACE>
<html>
<head><title>yoyoyoyo</title>
<body>
<p>is for 1

<p>is for 2

<p>is for 3

<p>is for 4

<p>is for 5

</body></html>

Note that full.ejs actually prints out the result of the include call.