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

express-ipn

v1.0.3

Published

Simple Express middleware for creating an IPN listener.

Readme

express-ipn

Create a PayPal IPN listener in minutes with this easy-to-use Express middleware.

##Installation

$ npm install express-ipn

##Usage

Mount the middleware on a POST handler on the endpoint where you want you IPN listener to live:

var app = require('express')();
var ipn = require('express-ipn');
var bodyParser = require('body-parser');

app.use(bodyParser.urlencoded({extended: false})); // IPN data is sent in the body as x-www-form-urlencoded data
app.post('/', ipn.validator(validationHandler));

function validationHandler(err, ipnContent) {
    if (err) {
        console.error("IPN invalid"); // The IPN was invalid
    } else {
        console.log(ipnContent); // The IPN was valid.
        ... // Process the IPN data
    }
}

...

when you are ready to go put your server into production, make the following change:

...
app.post('/', ipn.validator(validationHandler), true);
...

##API

var ipn = require('express-ipn');
ipn.validator(callback, [productionMode]);

callback will be called when the IPN verification protocol is complete. It will be passed two parameters: err and ipnContent. err will be an Error object if verification fails. Verification will fail under two circumstances:

  1. PayPal returned an INVALID message in response to the verification request, meaning the ipn is not valid
  2. A test IPN (such as from a sandbox account or the IPN simulator) was received when productionMode was enabled. This is to prevent a live server from handling fake data. Conversely, if productionMode is disabled, a live IPN will be treated as invalid, as non-development servers should not be handling live data.

If verification succeeds, err will be null. The content of the originally received IPN will be parsed as a JavaScript object and passed in the ipnContent parameter.

productionMode is an optional which should be set to true when the listener is ready to go into production, and handle live payment data. It defaults to false. Note the in order to handle test IPNs, such as those sent from sandbox accounts, or from the IPN simulator, productionMode must be false. Conversely, to handle live IPNs, productionMode must be set to true.