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

pinion

v0.0.0

Published

a 'connect' like library for handling generic req/rep pairs for anything you can think of

Downloads

6

Readme

Pinion

Connect like middleware framework for handling generic req, rep pairs. When I say generic, I mean literally anything can go as req and rep. Unlike connect, this framework doesn't have any concept of http, or routing built into it. Might add some configurable routing later.

Why? Pretty much just an experiment at the moment and to scratch an itch I have. Lots of room for improvements here. If it proves useful I might do something koa like with generators etc etc.

Usage

Create a pinion app

var pinion = require('pinion');
var app = pinion();

Add some middleware

Like connect, middleware should either take 3 args (req, res, next) in which case it will be standard handler, or 4 args (err, req, res, next) in which case it will be an error handler.


//normal middleware
app.use(function(req, res, next){
    if(req.id === undefined) {
        return next(new Error('id missing'));
    }
    console.log('message id:', req.id);
    console.log('message length:', req.message.length);
})

//error handler
app.use(function(err, req, res, next){
    console.error("something bad happened", err);
    //If we want to hand off to the next error handling middleware
    //next(err);
})

Sending a message into the app

This should work ok:

var req = {
    id: 1284,
    message: "here is some stuff"
};

var res = console.log;

app(req, res);

You should end up with some output like this:

message id: 1284
message length: 18

and this one should give us an error:

var req = {
		message: "watch me fail"
};

var res = console.log;

app(req, res);

and the output

[Error: id missing]

Todo

  • What to do about unhandled messages/errors
  • Sort out emitters usage
  • tidy up debug usage
  • TESTS!
  • More examples

##License

BSD 2 clause

Contributing

Open issues, send PRs, ask me questions on twitter (@sandfoxuk)