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

request-data

v1.4.1

Published

wraps any fn(request, response) function, parses the requests body, and calls the wrapped function with data as the last parameter.

Downloads

1,542

Readme

request-data

getRequestData(maxSize[optional], raw[optional], callback)

Wraps any fn(request, response) function, parses the requests body, and calls the wrapped function with data as the last parameter.

Normal usage:

"/myRoute": getRequestData(function(request, response, data) {
  // ...
});

With a named handler:

// Handler
function handleThing(request, response, data) {
  // ...
}

handleThing will be passed the arguments of request, response, data

"/myRoute": getRequestData(handleThing);

If you want to use it with a custom router that adds params after request/response, it will still work.

// beelin syntax

"/myRoute/`things`": getRequestData(function(request, response, tokens, values, data) {
  // ...
});

By default request-data will kill a request if you try and send it more than 1e6 bytes.

This can be overriden per handler:

getRequestData(1e10, function(request, response, data){
  // ...
});

Or globally:

getRequestData.maxRequestSize = 1e10;

If dataSize is greater than maxSize or data fails to parse during JSON.parse, the parse error is passed to the handler instead of data

You can handle this case by checking if data is an error:

"/myRoute":getRequestData(function(request, response, data){
    if (data instanceof Error) {
        // Bad request
        response.statusCode = 400;
        response.end();
        return;
    }

    // Otherwise, data was valid, and has been parsed.
});