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 🙏

© 2026 – Pkg Stats / Ryan Hefner

light-mock-server

v1.0.3

Published

Simple mock server

Readme

Documentation

This project contains a simple Mock Server for HTTP.

Pre requisites

  • npm >= 3.5.0
  • node >= 8.10.0

Building

Just run (it may require root or sudo access):

$ npm --global install light-mock-server

It will install the command mockserver globally, in the folder bin of node path.

To know more about global install, read this article: https://docs.npmjs.com/getting-started/installing-npm-packages-globally

Usage

$ lightmockserver [OPTIONS]
Options:
  -f [FILE], --file=[FILE]
    Read mock configuration from file (see example.json).
  -c [CONFIG], --config=[CONFIG]
    Specify mock configuration in command line.
  -p [PORT], --port=[PORT]
    Specify port to listen (default 3000).
  -h, --help
    Print help.

Examples:

Starting a mock server at port 8080 with configuration file:

$ lightmockserver -f example.json -p 8080

Starting a mock server at port 8080 with plain configuration:

$ lightmockserver -p 8080 -c '{"routes": [{"path": "/hello", "body": "world"}]}'

Mock configuration

The JSON format used by configuration is intuitive:

{
  "default404": {
    "body": {
      "message": "resource not found"
    }
  },
  "routes": [
    {
      "method": "get",
      "path": "/hello/:id",
      "status": 200,
      "body": {
        "message": "hello"
      }
    },
    {
      "method": "post",
      "path": "/world",
      "status": 201,
      "headers": {
        "content-type": "text/plain"
      },
      "body": "created"
    }
  ]
}

The default404 is optional and specify how the mock server will return responses for invalid routes (404).

The routes specifies an array of routes. Each one may have method, path, status, headers and body.

Note: the body can be a plain string or a JSON object.

Note: the path should be in the same format accepted by Express Framework (https://expressjs.com/pt-br/4x/api.html#path-examples).