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

rerequest

v0.2.1

Published

Creates fake HTTP request/response objects to send to Express.

Downloads

5

Readme

rerequest

This module creates fake (mock) HTTP request/response objects that you can feed in to an Express app. The entire request is handled in-process, meaning you don't waste time and resources making TCP connections to localhost.

Example

var express = require('express')
    , app = express()
    , Rerequest = require('rerequest')
    , rrq = new Rerequest(app);

app.get('/test-real', function(req, res) {
    res.send('I just return some text.');
});

app.get('/test-rerequest', function(req, res) {
    rrq.get('/test-real', function(result) {
        res.send('The other route returns ' + result.statusCode + ' and says ' + result.body);
    });
});

Everything that your rerequested route "writes" is buffered in memory, and when it calls res.end, your callback is called with the response object with a few things added:

  • res.body - a Buffer containing the body of the HTTP response (if there was one), or if the Content-Type header was set to application/json, the response body is automatically parsed and and you get an object.
  • res._content - always the raw body Buffer.

Most of the other normal response properties (like headers and statusCode) are of course available.

Options

rrq.post('/url', {
    session: req.session, // pass along the client's session object
    headers: {
        'Content-Type': 'application/x-www-form-urlencoded',
        'Host': req.host // if you're doing any vhosty type stuff
    },
    body: 'key=value&awesome=true', // Content-Length is automatically set
    socket: req.socket // copies socket.remoteAddress and friends to the rerequest
}, function (result) {
    // ...
});

If your app uses the session middleware, you must pass the client's session object (or an empty one), otherwise things break.