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

pwny

v0.4.0

Published

Module loader for Express

Downloads

19

Readme

pwny

Build Status

Pwny (pronounced pony) helps makes your Express apps modular and maintainable.

Installation

$ npm install pwny

Using pwny

Rather than this moderate mess:

var bodyParser = require('body-parser'),
    express    = require('express'),
    morgan     = require('morgan');

var app        = express();

app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));

morgan.token('type', function(req, res){ req.headers['content-type']; });

app.use(morgan('dev'));

app.listen(process.env.PORT || 1337);

You can clean things up using Pwny:

app.js

var express = require('express'),
    pwny    = require('pwny');

var app     = express();

pwny(app, {});

app.listen(process.env.PORT || 1337);

config/initializers/bodyParser.js

var bodyParser = require('body-parser');

module.exports = function(app, config) {
  app.use(bodyParser.json());
  app.use(bodyParser.urlencoded({ extended: false }));
};

config/initializers/morgan.js

var morgan = require('morgan')

module.exports = function(app, config) {
  morgan.token('type', function(req, res){ req.headers['content-type']; });

  app.use(morgan('dev'));
};

As you can see, Pwny allows you to keep your Express modules sparkly clean and logically separated.

Configuration

You can tell Pwny where to look by passing a path to the configPath option.

pwny(app, { configPath: 'config/middleware' });

Sometimes order matters. To specify an order in which your config files load you can pass in an order array.

pwny(app, { order: ['morgan', 'bodyParser'] });

Note that by specifying an order Pwny will only load specified files.

pwny(app, { order: ['morgan'] }); // will not load bodyParser

.pwnyrc

You can also configure Pwny by adding a JSON .pwnyrc file to your app's root directory.

{
  "configPath": "config/middleware",
  "order": ["morgan", "bodyParser"]
}