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

merver

v0.0.1

Published

A Mock API server that takes serves a YAML definition of sequenced APIs

Downloads

3

Readme

Merver

A simple sequence mock API Server. This is intended to make functional UI tests easier for SPA applications

Merver will serve API endpoints according to a YAML definition. What makes this different than other mock servers, is that you can have sequenced responses for your use cases. For example:

  1. POST /login fails with 403 (assumed bad credentials)
  2. POST /login succeeds the second time with 200 (assumed good credentials)
  3. GET /user/1 gives back a user with name = "Laura Johnson"
  4. PUT /user/1 gives back a user with name = "Laura Raghunath"
  5. GET /user/1 gives back a user with name = "Laura Raghunath"

Example YAML for above:

---
routes:
  "/login":
    POST:
      responses:
      - response:
          message: Invalid Password
        status: 403
      - response:
          id: 1
          name: Laura Johnson
        status: 200
  "/user/1":
    GET:
      response:
        name: Laura Johnson
    PUT:
      response:
        name: Laura Raghunath
      update:
        "/user/1":
          GET:
            response:
              name: Laura Raghunath

GET /_docs

This readme in in markdown

POST /_setup

{
    "YAML":"YAML Definition"
}

POST /_setup/file

{
    "path":"Absolute YAML File Path"
}

GET /_merver

{
    "rawYAML": "Raw YAML Text",
    "definition": {
        // JSON definition
    }
}