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

ui-http-mock

v1.0.1

Published

Mocking http calls for UI development

Readme

ui-http-mock

A lightweight CLI tool for mocking HTTP API endpoints during UI development. Define JSON response files in a simple directory structure and spin up a mock server instantly — no backend required.

Installation

Global — run ui-http-mock from anywhere:

npm install -g ui-http-mock

Local (recommended) — install as a dev dependency in your project:

npm install --save-dev ui-http-mock

Then add a script to your package.json:

{
  "scripts": {
    "mock": "ui-http-mock"
  }
}

Run it with:

npm run mock

No install — run once via npx:

npx ui-http-mock

Usage

ui-http-mock [options]

Options

| Option | Type | Default | Description | |---|---|---|---| | --port | number | 8080 | Port to listen on | | --mock-dir | path | mocks | Directory containing mock files | | --prefix | string | (none) | URL prefix for all routes | | --delay | number | 0 | Max random response delay in ms | | --help | — | — | Show help message |

Examples

ui-http-mock                              # Start on port 8080, load ./mocks
ui-http-mock --port 3000                  # Start on port 3000
ui-http-mock --mock-dir ./data            # Load mocks from ./data
ui-http-mock --prefix /api               # All routes prefixed with /api
ui-http-mock --delay 500                  # Add up to 500ms random delay

Mock File Structure

Organize mock files by route path and HTTP method. Each file is named after the HTTP method (lowercase) and contains the JSON response body.

mocks/
├── users/
│   ├── get.json          # GET /users
│   ├── post.json         # POST /users
│   └── [id]/
│       ├── get.json      # GET /users/:id
│       └── patch.json    # PATCH /users/:id
└── posts/
    └── get.json          # GET /posts

Dynamic Routes

Use [paramName] folder names to match dynamic URL segments:

mocks/
└── products/
    └── [id]/
        ├── get.json       # matches GET /products/1, /products/abc, etc.
        └── delete.json    # matches DELETE /products/1, etc.

Example Mock File

mocks/users/get.json:

[
  { "id": "1", "firstName": "John", "lastName": "Doe", "email": "[email protected]" },
  { "id": "2", "firstName": "Jane", "lastName": "Smith", "email": "[email protected]" }
]

Supported HTTP Methods

GET POST PUT DELETE PATCH

License

ISC