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

@earthtone/grayson-generator

v3.0.4

Published

Static Site Generator

Readme

Grayson Logo HTML Generator

ci status

Installation

npm install -g @earthtone/grayson-generator

Usage

grayson [options]

Options

  --help, -h        Output help info
  --version, -v     Output version number

  --input, -i       Source directory or file (defaults to current directory)
  --output, -o      Target directory (defaults to current directory)

  --mode, -m				Generation mode (defaults to "page")

Default options and metadata are overwritten by any options or additional metadata available in a project's package.json file via the grayson node.

{
	"name": "example-project",
	"version": "1.2.0",
	"description": "Example package.json File",
	"main": "index.js",
	"author": "Joe Schmoe",
	"license": "ISC",
	"grayson": {
		"input": "./md",
		"metadata": {
			"stylesheets": [
				"reset.css",
				"debug.css",
				"main.css"	
			],	
			"scripts": [ "bundle.js" ]
		}	
	}
}

Additionally, any options passed in via the command-line, overwrite options passed in via package.json.

Modes

Pages

Grayson's default mode presumes input will be a directory path to multiple MD files, and will generate one HTML file per MD file in the target directory. If a single MD file is given as input, Grayson will still generate one HTML file per MD file in the given directory. Each HTML file is prepended with a <nav> element, hyperlinked to all other generated HTML output.

Blog

If the --mode option is set to "blog", an additional index.html file will be generated (if none already exists), with a <nav> element.

Slides

If the --mode option is set to "slides", all MD files are concatenated into a single HTML file, housed in individual .slide containers. No <nav> element is prepended to the generated document.