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

dotall

v1.0.2

Published

Run doT (JavaScript template engine) over all files in a directory, including their filenames

Readme

Run doT (JavaScript template engine) over all files in a directory, including their filenames

This uses doT.js to walk through directories and parse all directory names, filenames, and file contents for doT templates with supplied data. See the doT.js documentation for more.

Installation:

npm i -s dotall

Using dotAll:

const dotAll = require('dotAll');

dotAll.renderDir('template_directory', {
  app: {
    name: "FlamingoApp"
  }
});

Methods:

.renderDir(templateDirPath, data)

The method renderDir walks through a directory and renders all files, directories, and filenames using doT. It takes two arguments:

argument name | data type | example --- | --- | --- templateDirPath | String | "path/to/templates" data | Object | { app: { name: "FlamingoApp" } }

.render(templateString, data)

The method render takes a string and renders it using doT. It takes two arguments:

argument name | data type | example --- | --- | --- templateString | String | "Welcome to the {{_self.app.name}}!" data | Object | { app: { name: "FlamingoApp" } }

Templates

Template tags are formed using two consecutive curly brackets and an underscore, and rely on self for data:

<h1>{{_self.app.name}}</h1>

Here's a list of automagically available properties of self:

FILENAME Name of the currently processed file, e.g. main.js FILEPATH Path of the currently processed file, e.g. C:\

Loops

You can loop through arrays and objects using two curly brackets followed by an asterisk:

<ul id="todo-list">
{{*todos :todo:index}}
    <li>{{_index}}.) {{_action}}</li>
{{*}}
</ul>

...combined with the following data:

const = { 
    todos: ['Cleanup', 'Refactor', 'Package'] 
}; 

...yields this rendered template:

<ul id="todo-list">
    <li>1.) Cleanup</li>
    <li>2.) Refactor</li>
    <li>3.) Package</li>
</ul>

Fallback

If the data path specified in a template couldn't be found, dotAll looks for a key called default in the data you passed and renders it instead. If no default key is provided, dotAll leaves these template tags untouched.