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

@dringtech/openapi-stubber

v0.7.0

Published

Auto-stubbing for OpenAPI V3 APIs

Downloads

8

Readme

openapi-stubber

Build Status Mutation testing badge

Auto-stubbing for OpenAPI V3 specs

This is a utility wrapper around openapi-backend aimed at rapidly standing up a stub server, primarily for testing purposes.

Installation

npm install --save-dev @dringtech/openapi-stubber

Usage

The loadStub and tearDown functions each return a promise, so can work nicely with async code.

Load the required stubs before running tests (or whenever).

const stubber = require('@dringtech/openapi-stubber');

await stubber.loadStub({
  name: 'Stub Name',
  spec: SPEC_DEF,
  port: 8000,
  stack: STACK,
  overrides: OVERRIDES,
  fixtures: FIXTURES,
  validateRequests: true|false
});

The spec (SPEC_DEF) can be anything that openapi-backend understands, primarily:

  • Path to an OpenAPI V3 file
  • An OpenAPI spec object

It is also possible to pass an optional overrides property to the loadStub call. This allows control over the example returned in response to a given path. The format is

{
  '/path/to/override': 'NameOfExampleInOpenAPISpec',
}

The examples must be defined in the OpenAPI Spec document.

Additional stack handling (e.g. setting headers) can be performed by passing in a stack property to the options. This must be a valid express middleware stack definition: either a single function with the signature (req, res, next), or an array of such functions.

Fixtures, over and above that supported by the OpenAPI examples, can be specified in the fixtures property. A full example of this is given below:

{
  '/path/to/override': {
    status: 'HTTP STATUS CODE',
    mock: 'DATA TO RETURN FROM CALL TO PATH',
    contentType: 'CONTENT TYPE TO SET'
  }
}

Only the mock property is required. status defaults to 200 and contentType defaults to application/json.

Requests to the stub backend will be validated by default. To override this behaviour, set the validateRequests property to false.

Once the tests (or whatever) are completed call the following code to clean up:

await stubber.tearDown();

Logging

If you want to log the stub output, call the following before any stubs are loaded:

stubber.setupLogging({ logFile: '/path/to/log/file.log' });