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 🙏

© 2024 – Pkg Stats / Ryan Hefner

mock-api-server

v0.4.6

Published

Mock out your API server for testing.

Downloads

124

Readme

mock-api-server

A flexible and powerful stand-in API server.

This server is meant to be booted quickly (for example, inside a test suite) in a Node.js process.

Booting

From the command-line:

./node_modules/.bin/mock-api-server --port PORT

To boot once for a test:

var MockApi = require('mock-api-server');
var api = new MockApi({"port": 7000});
api.start(function(err) {
  // ... do stuff ...
  api.stop();
})

To connect to an existing server:

var MockApi = require('mock-api-server');
var api = new MockApi({"port": 7000});
api.reset(); // Or whatever you want to do.

See test/server_test.coffee for more detailed examples.

If you are using Mocha, you can also boot the server in a before clause. It's also possible to boot the server once at the beginning of the test suite.

Options

The MockApi supports the following options:

Canned Responses

Canned responses live in your project's test/mock-api directory. This directory and its subdirectories has the same structure as your API. For example, to serve an endpoint /v2/foobizzle, populate the file test/mock-api/GET/v2/foobizzle.json.

Responding to HTTP Methods

Files in the test/mock-api/GET subdirectory are used for GET requests. Files in test/mock-api/PUT subdirectory are used for PUT requests, and so forth.

Responding to Query Parameters

If you have these three files:

test/mock-api/GET/v2/foobizzle.json
test/mock-api/GET/v2/foobizzle.json?type=search
test/mock-api/GET/v2/foobizzle.json?type=search&s=foo

then mock-api-server will serve the third one when type=search and s=foo are provided as query parameters. If only type=search is provided, the second one will be served--mock-api-server will take the most specific matching file.

* can be used to match zero or more characters. For example, the following file:

test/mock-api/GET/v2/foobizzle.json?type=*search*

Will match requests with a query parameter type containing a value "search" or "index,search" or "search,index".

Note that most shells will interpret ?, *, and &, so to create these files, you will have to backslash them. For example:

$ touch test/mock-api/GET/v2/foobizzle.json\?type=\*search\*\&s=foo

Live Responses

You can tell the API server to respond to a particular request like so:

api.respondTo('/foo/bar').with({status: 'OK', headers: {'access-control-allow-origin': '*'}});

This will be active until the next time api.reset() is called.

You can modify an existing response with:

api.respondTo('/foo/bar').byReplacing('foo.bar[1].baz').with([ 76 ]);