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

ts-mock-generator

v1.0.11

Published

Typescript mock generator

Downloads

39

Readme

English | 简体中文

✨ Features

  • 📦 Mock generation tool out of the box
  • 😛 Define the return value through the interface Interface automatically generates mock data
  • 📄 Support generating mock files for secondary editing
  • 🔥 Support file change monitoring (generated mock files, interface and request files)

📦 Installation

yarn add -D ts-mock-generator
npm install ts-mock-generator --save-dev

🔨 Example

import { MockDataResolver } from 'ts-mock-generator';

const resolver = new MockDataResolver({
  basePath: path.join(process.cwd(), 'src', 'apis'),
  configPath: path.join(process.cwd(), 'tsconfig.json'),
  mockDir: path.join(process.cwd(), 'src', 'mock'),
  includes: [/^.*Service/],
});

// Obtain mock data
resolver.getOrGenerateData();

resolver.watchMockFile(() => {
  // When mock.json changes, callback will be triggered
});

resolver.watchRequestFile(() => {
  // When interface and service change, callback will be triggered
});

Note: If you need to use a plug-in to generate mock data, please meet the following two requirements:

  • GET or POST accepts a generic return value, the first parameter of the method is url
  • GET or POST calls a general request method, the second parameter of the general request method is the general backend return body type

Such as:

class Request {
  get<T>(url: string, opts?: Record<string, any>) {
    return this.fetch<T>({
      method: 'get',
      url: `${url}?_t=${Date.now()}`,
      ...opts,
    });
  }

  post<T>(url: string, opts?: Record<string, any>) {
    return this.fetch<T>({
      method: 'post',
      url,
      ...opts,
    });
  }

  fetch<T, R = ResponseData<T>>(opts: Record<string, any>) {
    return new Promise<T>((resolve) => {
      resolve({} as T);
    });
  }
}

export default new Request();

⚙️ Configuration items

-basePath: The root directory to be parsed, please provide an absolute path

-configPath: The directory where the tsconfig.json file is located, used for parsing by the compiler

-mockDir: The location of mock file generation. When set, mock.json and structure.json will be automatically generated

-includes: The class name rules to be parsed, you can set a regular expression or an array of regular expressions

-excludes and includes are mutually exclusive, meaning type rules not to be parsed, generally not used