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

handler-agent

v0.2.0

Published

Zero-dependency (req,res) handler callback agent for use in client requests

Downloads

378,919

Readme

handler-agent

handler-agent creates a connection http.Agent usable by most HTTP clients that executes an HTTP handler (function (req, res) { res.end('hi') }) instead of creating a network connection.

The returned agent can be used by http.request(), got, and most other Node.js HTTP clients that support the use of http.Agents.

This is primarily useful for testing HTTP APIs without touching the network.

Usage

npm install --save handler-agent
const handlerAgent = require('handler-agent');

const myHttpHandler = (req, res) => {
	if (req.url === '/' && req.method === 'GET') {
		res.writeHead(200);
		res.end('Hello, world!');
	} else {
		res.writeHead(404);
		res.end('Not Found');
	}
};

const agent = handlerAgent(myHttpHandler);

const got = require('got').extend({
	agent: {
		http: agent,
		https: agent
	}
});

got.get('http://localhost/')
	.then(response => {
		console.log('GET /: Got response:', response.body);
	});

got.post('http://localhost/foo')
	.catch(err => {
		console.error('POST /foo:', err.stack);
	});

Output:

GET /: Got response: Hello, world!
POST /foo: HTTPError: Response code 404 (Not Found)
    at PromisableRequest.<anonymous> (/src/qix-/handler-agent/node_modules/got/dist/source/as-promise/index.js:124:28)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

But why?

Testing an HTTP API in modern tooling seems to fall in two extremes; you either use a bloated framework and desktop client, or you roll your own testing suite from scratch.

For me personally, I like rolling my own as I tend to put myself in unique scenarios that don't quite fit into the nicely specified boxes the larger frameworks prescribe.

This module is a good middleground; I'm able to use async/await with my favorite HTTP request library (e.g. got) without having to start a real TCP server and deal with all of the fragility that comes with it.

Using handler-agent prevents network issues such as re-used ports, latency (yes, really), managing port/host configuration, as well as removing the need for DNS lookups, modifying /etc/hosts just to test the Host header, etc.

License

Copyright © 2020 by Josh Junon. Released under the MIT License.