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

@kaluza/mock-server

v0.12.1

Published

A testing library that lets you spin up a real Express-based server during tests, to stub out and check the requests made to the systems your application interacts with.

Downloads

149

Readme

Node Mock Server

A testing library that lets you spin up a real Express-based server during tests, to stub out and check the requests made to the systems your application interacts with.

Usage

An example of a minimal server setup:

import mockserver from "@kaluza/mock-server";

// Create a server on port 8000
const server = mockserver(8000);

// Define some stubbed endpoints
const endpoint = server.get("/path", { status: "OK" });

// Start the server
await server.start();

// Run some code that makes a request to /path
await fetch("http://localhost:8000/path");

// Check the request
console.log(endpoint.calls.length === 1);

// Stop the server
await server.stop();

Reference

mockserver()

mockserver(port, [options])

Creates a new MockServer object with options. Only one path is registered: /mockserver.

Options object:

  • enableLogging - logs out events such as endpoint registration, requests made. Defaults to false
  • useHttps - creates a https server.
  • sslCertDir - the directory the https server looks in for the self-signed certificate files server.key and server.cert.
  • middleware - an array of Express middleware that will be applied to all routes in the server.

MockServer

server.get(path, response, [responseStatus])

Registers a GET endpoint for the given path, returning an EndpointRecord.

  • path is an Express-compatible path
  • response can be either an object, which will be returned as JSON, or an Express-compatible request handler. This lets you vary the response based on what's in the request. This can also be a number, which will be used as a response status code if the request should not have any content.
  • responseStatus can optionally be provided to specify a response status code, this defaults to 200 if not set.

If two endpoints are created on the same path, the most recently created one will take precedence.

server.post(path, response, [responseStatus])

Registers a POST endpoint for the given path, returning an EndpointRecord.

  • path is an Express-compatible path
  • response can be either an object, which will be returned as JSON, or an Express-compatible request handler. This lets you vary the response based on what's in the request. This can also be a number, which will be used as a response status code if the request should not have any content.
  • responseStatus can optionally be provided to specify a response status code, this defaults to 200 if not set.

If two endpoints are created on the same path, the most recently created one will take precedence.

server.patch(path, response, [responseStatus])

Registers a PATCH endpoint for the given path, returning an EndpointRecord.

  • path is an Express-compatible path
  • response can be either an object, which will be returned as JSON, or an Express-compatible request handler. This lets you vary the response based on what's in the request. This can also be a number, which will be used as a response status code if the request should not have any content.
  • responseStatus can optionally be provided to specify a response status code, this defaults to 200 if not set.

If two endpoints are created on the same path, the most recently created one will take precedence.

server.reset()

Resets the server, creating a new express instance with no endpoints registered except the default /mockserver. Can be used to clean up if re-using a server between test suites.

server.stop([options])

Stops the server, preventing it from receiving any new connections.

Options object:

  • force - whether to force stop the server, closing any connections that are still open. Defaults to false.

EndpointRecord

Returned when an endpoint is registered. It lets you make assertions against calls to the server.

record.calls

An array of CallRecords. These are objects with the following properties:

  • params - the path params in the request
  • query - the query params in the request
  • headers - the request headers
  • body - the request body, for calls that have one