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 🙏

© 2024 – Pkg Stats / Ryan Hefner

unfold

v0.4.2

Published

Static Site Generator

Downloads

7

Readme

unfold

A data-driven static site generator.

  • Supports handlebars templates.
  • Supports custom partials and helpers for handlebars.
  • Supports SASS now with Autoprefixer!

Usage: unfold site.json

NPM script example (package.json in your project):

"build": "unfold site.json"

The site.json file should look like:

{
	"sourceDirectory": "src",
	"destinationDirectory": "dest",
	"dataDirectory": "data",
	"partialsDirectory": "partials",
	"helpersDirectory": "helpers",
	"data": {
		"layout": "layout.html.hbs"
	}
	"pages": {
		"src/specialPage.html.hbs": {
			"layout": "specialLayout.html.hbs"
		}
	}
}

Site Specification

sourceDirectory: The directory storing the original version of the site. Handlebars templates and SASS files in this directory will be processed and output to destinationDirectory. All other files will be copied to destinationDirectory unmodified.

destinationDirectory: The "unfolded" output version of the site.

dataDirectory: All JSON files in this directory will be merged into the data field with a key of their filename without the .json.

partialsDirectory: A directory containing Handlebars partials. Example: a file named _something.html.hbs will be loaded as a partial named something and available for use in handlebars as {{>something}}.

helpersDirectory: A directory containing handlebars helpers. Example: a file named something.js will be loaded as a helper named something and available for use in handlebars as {{something}}. Helper files should export a single function.

data: Data available to the handlebars templates. layout is a special key that specifies a layout template to wrap around the current file. The handlebars file specified in layout should contain a reference to the {{>body}} partial where the current page will be loaded.

pages: Per-page data that overrides keys in data and is made available to handlebars templates.