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

endpoint-response-override

v1.1.2

Published

The module will override an endpoint response, it is used in the integration tests for express server application

Readme

endpoint-response-override

A simple tool which allows you to override the endpoint responses of your express server. It is useful when you want to test the front end behaviour based on different server responses. for example you can use it to test the NextJs server side rending scenarios.

usage

setup

setup example (for details check example folder]):

const jsonServer = require('json-server');
const initialData = require('./db.json');
const { overrideRouter, responseOverrideMiddleware } = require('endpoint-response-override');

const server = jsonServer.create();

const router = jsonServer.router(initialData);

const middlewares = jsonServer.defaults();

// here to add override middleware
server.use(responseOverrideMiddleware);

server.use(middlewares);
server.use(jsonServer.bodyParser);

// add the override route
server.use('/override', overrideRouter);
server.use(router);

const PORT = process.env.PORT || 3000;
server.listen(PORT, () => {
  console.log(`JSON Server is running on port ${PORT}`);
});

register endpoint response

POST /override/register body:

{
    "url": "/users",
    "method": "GET",
    "response": {
        "status": 200,
        "body": {
            "name": "batman"
        }
    }
}

response status code: 200 After this when you call GET /users, then the server will return status 200 with body

{
    "name" : "batman"
}

clear the override response

POST /overide/reset response status code: 200 This endpoint will clear all the override responses.

parallel register / override

add Header x-parallel-index in each request, include /register and /reset, this feawture is useful when mocking server side response in the playwright tests