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

mocksrv

v1.0.0

Published

Mock server for REST APIs

Downloads

5

Readme

Mock-server

The mock-server is able to run as a stand-alone app.

Running the mock-server

Configuration

By default, the mock-server runs on http://localhost:9100. You can configure the port by modifying the package.json file:

  • config.port: the mock-server will run on this port http://localhost:[config.port]/

Folder structure

  • mocks: contains a folder structure that represent resource_uris

Example:

The request for

/search/api/v1/search/

will be parsed to

+ /
  + mocks
    + search
      + api
        + v1
          + search
            - index.js (a function that returns a JSON object)

Writing a mock

Based on the above example

Step 1:

Create the folder structure that represent an endpoint

Step 2:

Create an index.js file - (files named index.js will be picked up as modules by the NodeJS module manager)

Step 3:

Write the actual mock:

var equal = require('deep-equal');

module.exports = function (query, req, res) {
    return {
        a: 'a'
    };
};

where the arguments for the function are:

The above solution allows you to return different JSON objects based on different query arguments.

Example mock for /example/api/v1/search/?sort=asc (assuming that we have ascMock.json, descMock.json and filtered.json files in the same folder as the index.js is):

mocks/example/api/v1/search/index.js
var equal = require('deep-equal');

var mocks = [{
    params: { 'filter': 'mediaType:video' },
    mock: require('./filtered.json')
}, {
    params: { sort: 'asc' },
    mock: require('./ascMock.json')
}, {
    params: { sort: 'desc' },
    mock: require('./descMock.json')
}];

module.exports = function (query, req, res) {

    var filtered = mocks.filter(function(mock){
        return equal(mock.params, query);
    });

    return filtered[0].mock;
};

This mock allows for multiple different responses based on query params without having much logic. This file can be found at

!!! Very important !!!

Mocks should not contain any logic at all, so please, keep it simple!!!

Example project

Examples of creating mocks can be found in the example app mocks in mocks/example