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

express-hijackresponse

v0.2.1

Published

Rewrite HTTP responses on their way out.

Downloads

63

Readme

express-hijackresponse

Module that allows you to rewrite HTTP responses from middleware further down the stack, such as static providers, HTTP proxies etc.

It's mostly useful for content filters. The original use case is injecting an inline JavaScript into all HTML responses in LiveStyle.

Installation

Make sure you have node.js and npm installed, then run:

npm install express-hijackresponse

Usage

Requiring the module installs a hijack method on your response objects:

var express = require('express');
require('express-hijackresponse');

var app = express.createServer();

// ...

app.use(function (req, res, next) {
    res.hijack(function (err, res) {
        if (err) {
            res.unhijack(); // Make the original res object work again
            return next(err);
        }
        // 'res' is now a fake response object with `writeHead`,
        // `write`, `end`, `getHeader`, `setHeader`, `removeHeader` methods.

        if (/^text/html(?:;$)/.test(res.getHeader('Content-Type'))) {
            // Don't hijack HTML responses:
            return res.unhijack();
        }
        res.setHeader('X-Hijacked', 'yes!');
        res.removeHeader('Content-Length');

        // It emits 'data' and 'end' events representing the original response:
        res.on('data', function (chunk, encoding) {
            // The original response emitted a chunk!
        }).on('end', function () {
            // The original response ended!
            res.end('Sorry, your data was hijacked!');
        });
    });
    // next() must be called explicitly, even when hijacking the response:
    next();
});

Example

Rewrite all JSON responses so they're wrapped into a {"foo": ...} literal:

var express = require('express');
require('express-hijackresponse');

express.createServer()
    .use(function (req, res, next) {
        if (req.accepts('json')) {
            res.hijack(function (err, res) {
                if (err) {
                    res.unhijack(); // Make the original res object work again
                    return next(err);
                }
                // Inspect the original response headers to see if we actually want to rewrite the response:
                if (/\/json$/.test(res.getHeader('Content-Type'))) {
                    // Remove Content-Length if it's there (it won't be correct when the response has been rewritten):
                    res.removeHeader('Content-Length');
                    res.writeHead(res.statusCode);
                    res.write('{"foo":');

                    // Stream the original response and slip in a '}' before ending:
                    res.pipe(res, {end: false});
                    res.on('end', function () {
                        res.write('}');
                        res.end();
                    });
                } else {
                    res.unhijack();
                }
            });
        }
        next();
    })
    .use(express.static(__dirname))
    .listen(1337);

TODO

Better error handling, backpressure support when streaming.

License

3-clause BSD license -- see the LICENSE file for details.