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

fake-json-server

v1.0.1

Published

Simple fake json server for `GET`, `POST` only. Each api call only returns `json data`. It fits if you simply verify your api call works with return value.

Readme

Fake Json Server

Simple fake json server for GET, POST only. Each api call only returns json data. It fits if you simply verify your api call works with return value.

Argument

Port number can be set with -p option. (default: 8080)

npm start -p 8888

routes.json

You can define url in this file like below.
Root key can be either get or post and its value is an array consisting of object with route and key

{
  "get": { # determine get or post
    "routes": [
      { "route": "/api/photos", "key": "getPhotos" },
      { "route": "/api/names/:id", "key": "getNames" }
    ]
  },
  "post": { # determine get or post
    "routes": [
      { "route": "/api/photos", "key": "postPhotos" },
      {
        "route": "/api/names",
        "key": "getNames"
      }
    ]
  }
}

data.json

Root key should be identical to the value that is in routes.json.
For example, getPhotos in data.json comes from get.routes.key in routes.json

{
  "getPhotos": {
    "photo": "photo.jpg"
  },

  "getNames": {
    "name": "young"
  },

  "postPhotos": {
    "result": "ok",
    "photo": "photo.png"
  },
  "postNames": {
    "result": "ok",
    "name": ["young", "ddong"]
  }
}

Call the url

GET http://localhost:8080/api/photos
GET http://localhost:8080/api/names
GET http://localhost:8080/api/names/user-id

POST http://localhost:8080/api/photos
POST http://localhost:8080/api/names