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

modern-mirror

v1.0.1

Published

A simple server that makes mocking production servers more feasible

Downloads

4

Readme

Modern Mirror

Description

There have been multiple times in my development career where I've just needed something to serve a very specific response. Usually because the actual server I'd be requesting from doesn't have a sandbox, or it is currently unavailble for a variety of reasons. Enter Modern Mirror. Modern Mirror let's you quickly "Mock" a server by dropping files in a directory that contain the content you want to be returned.

Installation

npm install -g modern-mirror

Usage

To start the server run modern-mirror

Modern Mirror accepts the following arguments:

  • -p --port the port that Modern Mirror should run on (defaults to 3000)
  • -d --route-directory the directory that Modern Mirror should use for its routes (defaults to ~/modern-mirror-routes)

Simple Route Example

  • Start the server with modern-mirror
  • Place a file titled test.json in the ~/modern-mirror-routes/ directory or whatever directory you specified with -d/--route-directory
  • Make any kind of request (Modern Mirror doesn't care if it is a GET, POST, PUT, etc.) to localhost:3000/test
  • The response should be the contents of the test.json file you created earlier

Nested Route Example

Proper REST apis don't operate right off of the domain. Most urls will look like this: localhost:3000/api/customers/1?firstName=hesto2. To support this kind of url, you will need to do the following:

  • Create a folder in your routes folder titled api
  • In the api folder, create another folder titled customers
  • In the customers folder place a file titled 1.json, or if you wanted to be more specific you can do 1?firstName=hesto2.json

Query Params

If you don't want to include the query params in the file name, Modern Mirror will return the content of the first file matching customer*. Having the query params in the file name will allow you to return different responses if your app makes requests with varying params.