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

jigglypuff

v0.0.23

Published

Fake terminus pampas web container

Downloads

72

Readme

Fake Aixforce Web Container

requirements

  • nodejs: ~0.10 (with npm)

usage

First, install jigglypuff use git repo url or local path.

npm install -g jigglypuff

Second, run it.

jiggly

help:

jiggly -h

config

jigglypuff can accept a config file named jiggly.json under the work path.

options

All options has default value below:

{
  "serverPort": 8080,
  "filesHome": "public",
  "viewsHome": "public/views",
  "componentsHome": "public/components",
  "dataFile": [],
  "extraHelpers": [],
  "oldMode": false,
  "pageMode": false
}

The config file (jiggly.json) can include multiple option groups. Depend on env variable NODE_ENV, one group will be loaded.

ex:

{
  filesHome: "public",
  "env": {
    "dev": {
      "serverPort": 8081
    },
    "prod": {
      "serverPort": 80
    }
  }
}

All unset options will use the default value.

workflow

  1. leave all .js files in lib/ folder there
  2. write code with coffee in src/ folder
  3. write test code with coffee in test/ folder
  4. run npm test, make sure all tests passed
  5. use npm run compile to compile coffee to js
  6. commit and push to git

To compile and install the repo, use npm run build.

use mock data

Write a .js file and setting the option dataFile to point to it.

The data file may like below:

module.exports = {
  "/api/test": {
    data1: "some data",
    data2: "some data2",
    data3: ["11", "22", "33"]
  },
  "/api/test2": function(params, method) { // method: GET, POST, PUT, DELETE...
    return {
      data1: params.p1,
      data2: params.p2
    };
  }
}

Export your datas with url:object/function pair. And if functions provided, all the request params in form and query will be passed in.