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

piwwi

v0.2.1

Published

A JSON blog with Mongod comments, developed to run on OpenShift

Downloads

22

Readme

piwwi

A JSON-based blogposts and Mongod-based comments, developed to run on Node.js Express (I use it on OpenShift).

Getting started

Include it in your server.js or whatsoever entry point of your app:

var piwwi   = require('piwwi');

Then connect to your Mongod instance with a string like:

piwwi.mongod('mongodb://user:[email protected]/Comments');

Or skip the connection if mongod not available:

piwwi.mongod('', 'no');

Define a sample notes.json like the following and put into the Express root:

[
  { "current" : "0002" },
  { "why-node-js" : 
    {
      "jade": "0001",
      "url": "why-node-js",
      "title": "Who uses Node.js and why",
      "subtitle": "Revolutioning your perception of www",
      "date": "2013-06-19",
      "keys": "node, javascript, www",
      "published": "yes"
    }
  },
  { "" : 
    {
      "jade": "",
      "url": "",
      "title": "",
      "subtitle": "",
      "date": "4",
      "keys": "",
      "published": ""
    }
  }
]

Add the blog functions to your routes, for instance the posts list:

app.get('/blog', function(req, res) {
    piwwi.blogIndex(res);
}

And the post:

app.get('/blog/:title', function(req, res) {
    piwwi.blogPost(res, req.params.title.toString());
});

The posts list is an example view you can find in views/blog_index_example.jade, while each post is a jade named as xxxx.jade (example in views/blog_post_example.jade). Post views are organized by default in the views/notes/ application directory.

You can configure in the header of lib/piwwi.js:

The file containing the posts list:

var jsonfile      = 'blog.json';

Your blog posts locations (so it's /views/blog/ in the example):

var viewdir       = 'blog';
var relativeviews = '../../../views';

The mongodb connection string:

var mongoconf      = 'mongodb://127.0.0.1/Comments';

TODO

  • RSS
  • Flash messages
  • Play with Socket.IO