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

msw-auto-mock-ts

v0.4.0

Published

Generate random typescript typescript mock data from OpenAPI specification for msw.

Downloads

41

Readme

msw-auto-mock-ts

npm npm

A cli tool to generate random typescript mock data from OpenAPI specification for msw.

Why

Since we already have all the type definitions from the OpenAPI specification, manually writing each response resolver is entirely unnecessary.

Getting Started

We typically use tools like openapi-generator-cli to create an HTTP client based on OpenAPI specification. These tools also generate all the necessary request and response models. Our goal is to reuse those models and automatically mock all API response data. Assuming we already have all the request and response models in our project, let’s see how it works.

Usage

This tool also requires @faker-js/faker >= 8 and msw >= 2.

Install:

npm add msw-auto-mock-ts @faker-js/faker -D

Read from your OpenAPI specification, locate the models folder or file (relative to the output path), and then generate the output code:

# can be http url or a file path on your machine, support both yaml and json.
npx msw-auto-mock-ts http://your_openapi.json -o ./mock --related-model-path ../api/models -camel --handler-name openApiHandler.ts

Then we will get a handler file such as 'openApiHandler.ts' which contains all mocked APIs and responses like below:

export const openApiHandler = [
  http.post<never, ApiReqBaseWalletTransferReq>(
    `${baseURL}/api/v1/trans/walletTransfer`,
    async ({ request }) => {
      const req = await request.json();

      // modify walletTransferHandler function to override the response
      const response = await walletTransferHandler(req);
      if (response) {
        return response;
      }

      const res = await getWalletTransfer200Response();
      return HttpResponse.json<ApiResBaseWalletTransferRes>(res);
    },
  )
  // others ...
]

It also creates an override handler, such as 'walletTransferHandler' in the example, allowing users to add customized responses. The override handler file is located in a subfolder and will not be overwritten unless the file is deleted before regenerating mock data.

const walletTransferHandler = async (request: ApiReqBaseWalletTransferReq) => {
  // disable this handler
  return null;

  // await delay(200);

  // return new HttpResponse(null, {
  //   status: 500,
  //   statusText: "Internal Server Error",
  // });

  // const response: ApiResBaseWalletTransferRes = { };
  // return HttpResponse.json<ApiResBaseWalletTransferRes>(response);
};

export default walletTransferHandler;

The final step is to use 'openApiHandler.ts' to integrate with msw, see Mock Service Worker's doc for more detail.

Options

  • -o, --output: specify output file path or output to stdout.
  • --handler-name <ts-file-name>: Output handler file name. e.g. handlers.ts
  • --related-model-path <directory>: Path to request / response model folder or file (export all models) related to handler file location. e.g. ../api/models
  • --camel: Transform request/response type to camelCase. e.g. myVISACard -> myVisaCard
  • -m, --max-array-length <number>: specify max array length in response, default value is 20, it'll cost some time if you want to generate a huge chunk of random data.
  • -t, --includes <keywords>: specify keywords to match if you want to generate mock data only for certain requests, multiple keywords can be separated with comma. e.g. -t keyword1,*keyword2,*keyword*
  • -e, --excludes <keywords>: specify keywords to exclude, multiple keywords can be separated with comma. e.g. -e keyword1,*keyword2,*keyword*
  • --base-url: output code with specified base url or fallback to server host specified in OpenAPI.
  • -h, --help: show help info.