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

roam-swagger-mock-server

v1.0.7

Published

Mock server toolkit that uses Swagger and TypeScript

Downloads

27

Readme

roam-swagger-mock-server

An npm module and cli tool that provides quick and easy way for creating full or partial mock of Sauce backend APIs.

Installation

The module is supposed to be installed globally:

npm i roam-swagger-mock-server -g

Usage

  • Create a folder with swagger.json
  • Run swagger-mock init
  • Edit index.ts for your needs
  • Run swagger-mock to start mock server

Mock implementation

After running init you will see a generted index.ts file. That file contains a blank class for your mock controller:

import {IMockSauceController, start} from './mock-interface';
import {ReqContext} from 'roam-swagger-mock-server';

class Controller implements Partial<IMockSauceController> {
    //put your implementation here if needed
}

start(new Controller(), { 
    port: 4000,
    proxy: 'http://localhost:3000'
});

There are three ways to operate the mock:

  1. Simple JSON file response
  2. Custom implementation
  3. Proxying to real API

Mock server follows logic: first, it tries to find method implementation in your Controller, then it tries to find mock JSON file within your folder (.json), finally it tries to proxy it to original API.

Simple JSON file response

Place a json file named <methodName>.json anywhere within your folder.

Example: Your API has a method getPetById (taken from swagger pet store).

getPetById.json

{
  "petName": "Harry",
  "petType": "parrot"
}

Custom implementation

In this example, we are mocking getPetById method from the API with our own implementation.

Depending on provided petId mock server will return different results:

import {IMockSauceController, start} from './mock-interface';
import {ReqContext} from 'swagger-mock-server';

class Controller implements Partial<IMockSauceController> {
    async getPetById(reqContext: ReqContext, petId: number): Promise < any > {
        if (petId == 1) {
            return {
                "petName": "Harry",
                "petType": "parrot"
            }
        } else {
            return {
                "petName": "Potter",
                "petType": "parrot"
            }
        }
    }
}

start(new Controller(), { 
    port: 4000,
    proxy: 'http://localhost:3000'
});

Custom implementation and proxying at the same time

In this example, we are mocking getPetById method from the API with our own implementation but only for certain petId, all other id requests get flow to the original API.

import {IMockSauceController, start} from './mock-interface';
import {ReqContext} from 'swagger-mock-server';

class Controller implements Partial<IMockSauceController> {
    async getPetById(reqContext: ReqContext, petId: number): Promise < any > {
        if (petId == 1) {
            return {
                "petName": "Harry",
                "petType": "parrot"
            }
        } else {
            return reqContext.proxy();
        }
    }
}

start(new Controller(), { 
    port: 4000,
    proxy: 'http://localhost:3000'
});