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 🙏

© 2025 – Pkg Stats / Ryan Hefner

echo-server-with-api

v1.0.3

Published

a simple http echo server

Readme

Build Status

echo-server-with-api

a simple http echo server that can be started and stopped programmatically through an API to help testing http clients

  • all http requests are answered with a 200 OK status code, and a JSON representation of the request data as the body of the request (echo)

  • add ?status=xxx to the request url to have the server respond with xxx as the http-status-code (you still get the echo as the response body)

  • add ?timeout to tell the server to time-out your request (useful for testing how your http client handles server timeouts)

  • unlike node's built-in http server, this echo server also closes all active connections (Keep-Alive) when calling .stop(), so the server really stops - instead of just "stops accepting new connections while keeping active connections alive"

  • meant as an easy-to-use test server for http clients, with Mocha in mind (start \ stop the server from within mocha)

  • supports query-string, cookies, form \ JSON payload, and more

  • also provides a synchronous start \ stop API


Install

npm install echo-server

Usage

const echoServer = require('echo-server');

// before your tests
echoServer.start(() => {
    console.log('serving echo @ ' + echoServer.location);
});

//
// test your http client by sending requests
// to the echo-server and running assertions on
// the resulting "echo" to make sure your client
// sends the expected HTTP requests, and properly
// handles the various response codes, timeouts, and payloads
//


// after your tests you can gracefully close the server
echoServer.stop((err) => {
    if (err) {
        console.log('boo..'); // this should never happen
    }

    console.log('echo server stopped');
});

Example of an Echo-Response

POST http://localhost:54606/foo/bar?my=query PAYLOAD qwe=asd

{
    clientIP: '127.0.0.1',
    url     : '/foo/bar',
    method  : 'post',
    protocol: 'http',

    query   : {
        my: 'query'
    },

    cookies : {},

    headers : {
        'content-type'  : 'application/x-www-form-urlencoded',
        'content-length': '7',
        host            : 'localhost:54606',
        connection      : 'close'
    },

    body: {
        qwe: 'asd' }
    }

API

start([callback])

starts the echo server. if a callback is used it will run once the server is up and running (listening for incoming requests)

startSync()

starts the echo server synchronously. this is just a convenience method if you need a sync API instead of using async patterns (callbacks \ promises \ other)

stop([callback])

stops the echo server. if a callback is used it will run once the server has fully stopped (all active connections were destroyed and new connections cannot be made)

stopSync()

like stop(), just synchronously

location

the url where the server can be reached. normally this is something like http://localhost:1234. when the server is not running, this is an empty string

isListening

a boolean. true when the server is running. false otherwise


Test

npm run test

Related