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

noisey

v1.0.0

Published

A simple static site generator using template literals, with incremental builds.

Readme

#A simple static site generator for Node

This library is in extremely early development and has no error handling

##To use:

Install noisey globally ``````npm i -g noisey```

Make a new directory and navigate to it.

Run the following:

npm init

noisey init

This will create two directories - templates and pageData.

Files in pageData should export an array of objects in the following format:

pageData/test.js

const data = [
  {
    fileName: 'test_second', // The name of the html file to be created
    directory: 'build',      // The directory to build the file in
    template: "test",        // The name of the template html file in the templates directory
    data: {                  // Any template variables to be passed to the template
      text: 'Hello world!'
    }
  }
]
module.exports = data;

Data can be acquired from whatever source you want - databases, AJAX, etc. A corresponding template should exist in the templates directory.

Templates are just html files with template literals to insert variables from a pageData file.

templates/test.html:

<h1>${text}</h1>

In this case, each test.js object will create a corresponding html file with the ${text} string replaced with "Hello world!"

To perform a build of the entire site (using all of your pageData files and corresponding templates), run: noisey build

To perform a build only of specified files, run: noisey build dataModule1 dataModule2 etc.

In our example, to build only test.js we would run: noisey build test