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

markheim

v2.0.1

Published

Based on Gulp, inspired by Jekyll...it's Markheim, the killer static site generator for everyone.

Downloads

24

Readme

Markheim

The killer static site generator for everyone.

http://en.wikipedia.org/wiki/Markheim

Configuration Files

The first configuration file that's loaded contains Markheim's own settings, and is located at config/default.yml. This tells us which SSG layout we are using. For example:

ssg: jekyll

Then we load Markheim's own default values for the corresponding SSG. This file will also be in the config directory.

Then we load the SSG's own default values. These settings could have been placed directly into the file loaded in the previous step but by loading the SSG defaults in two steps we're able to make use of any default files that an SSG might provide. In the case of Jekyll the defaults/jekyll.yaml file is taken directly from the Jekyll project.

Finally, we can load the settings for a particular site. The location of these settings will usually come from the Markheim defaults for the SSG (config/jekyll.yaml, for example) rather than the SSG's own defaults (defaults/jekyll.yaml) since these kinds of settings will usually be hard-coded.

Build a Site

$ markheim build
# => The current folder will be generated into ./_site

Sample run:

$ markheim build
[18:52:58] Configuration file: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site/_config.yml
[18:52:58]             Source: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site
[18:52:58]        Destination: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site/_site
[18:52:59]       Preprocessing...
[18:53:03]       Generating...

Build and Serve a Site Locally

$ markheim serve
# => The current folder will be generated into ./_site and then served with BrowserSync

Sample run:

$ markheim serve
[18:53:23] Configuration file: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site/_config.yml
[18:53:23]             Source: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site
[18:53:23]        Destination: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site/_site
[18:53:23]       Preprocessing...
[18:53:27]       Generating...
[BS] Access URLs:
 -------------------------------------
       Local: http://localhost:4000
    External: http://192.168.1.13:4000
 -------------------------------------
          UI: http://localhost:4001
 UI External: http://192.168.1.13:4001
 -------------------------------------
[BS] Serving files from: /Users/markbirbeck/Documents/workspace/_norepo/my-awesome-site/_site
[BS] Watching files...

Destination folders are cleaned on site builds

The contents of destination are automatically cleaned, by default, when the site is built. Files or folders that are not created by your site will be removed. Files and folders you wish to retain in destination may be specified within the keep_files configuration directive.

Do not use an important location for destination; instead, use it as a staging area and copy files from there to your web server.