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

whipsnap

v0.1.1

Published

Build a website focussed around posts, super simple and all in JS

Downloads

2

Readme

Whipsnap

Whipsnap is a JS based content generator. With a preference towards posts and static website. This is currently a work in progress

Install

# CLI
npm i -g whipsnap
npm i --save whipsnap

Usage

Whipsnap can be used via CLI or as part of an application. You will need to configure your project in the following structure. An output directory will be created called out/ containing a static website.

assets/
    stylesheets/
        whipsnap.css         Main CSS file (At present defauls to github bootstrap css)
config/
    index.js                Configuration file, usage will be describe below.
pages/
    xxx.md                  The pages directory will contain static pages which will be pulled in and able to be referenced.
posts/
    YYYY-MM-DD.md           These are `blog` posts that will be displayed on the main page.

CSS - All CSS should go into a single file - whipper.css within the stylesheets folder.

Configuration - Represented by config.js or config/index.js module.

Navigation - All information will be contained within the key navigation and will configure the navigation bar.

module.exports = {
  navigation: {
    brand: {
      text: 'AB',
      value: 'index',
    },
    items: [
      {
        text: 'Home',
        value: 'index',
      },
      {
        text: 'About Me',
        value: 'about-me',
      },
      {
        text: 'Contact',
        value: 'contact',
      },
    ],
  },
};

Pages - Static pages such as About Me which should be written in Markdown and will be auto compiled.

Posts - Will appear in a listed format on the home page.

CLI

whipsnap build -d path/to/directory

Node

require('whipsnap').build(__dirname)