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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@dota2classic/nest-openapi-client-generator

v0.0.7

Published

OpenAPI spec and client generator for NestJS microservices

Readme

@dota2classic/nest-openapi-client-generator

Generates OpenAPI specs from NestJS microservices without requiring infrastructure (no DB, Redis, RabbitMQ connections needed).

Uses @nestjs/testing's useMocker() to auto-mock all dependencies.

Installation

yarn add -D @dota2classic/nest-openapi-client-generator

Usage

1. Create a generator script

Create scripts/generate-openapi.js in your microservice:

const { runGenerator } = require("@dota2classic/nest-openapi-client-generator");
const { AppModule } = require("../dist/src/app.module");

runGenerator(AppModule, {
  title: "GameServer API",
  description: "Matches, players, MMRs",
  version: "1.0",
  tags: ["game"],
  bearerAuth: true,
});

2. Add npm script

{
  "scripts": {
    "openapi:generate": "node scripts/generate-openapi.js"
  }
}

3. Run after build

yarn build && yarn openapi:generate ./openapi.json

API

generateOpenApiSpec(appModule, options)

Returns the OpenAPI document as an object.

import { generateOpenApiSpec } from "@dota2classic/nest-openapi-client-generator";

const spec = await generateOpenApiSpec(AppModule, {
  title: "My API",
  description: "Description",
  version: "1.0",
  tags: ["tag1", "tag2"],
  bearerAuth: true,
});

generateOpenApiSpecToFile(appModule, options, outputPath)

Generates and writes the spec to a file.

import { generateOpenApiSpecToFile } from "@dota2classic/nest-openapi-client-generator";

await generateOpenApiSpecToFile(AppModule, options, "./openapi.json");

runGenerator(appModule, options, outputPath?)

CLI helper that handles process exit codes. Use this in your generator script.

import { runGenerator } from "@dota2classic/nest-openapi-client-generator";

// outputPath defaults to process.argv[2] or "./openapi.json"
runGenerator(AppModule, options);

CI/CD Example

# .github/workflows/generate-api-client.yml
name: Generate API Client

on:
  push:
    branches: ["master"]

jobs:
  generate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: 20.x

      - run: yarn install
      - run: yarn build
      - run: yarn openapi:generate ./openapi.json

      - uses: actions/upload-artifact@v4
        with:
          name: openapi-spec
          path: openapi.json

How it works

  1. Creates a NestJS testing module with your AppModule
  2. Uses useMocker(() => ({})) to auto-mock ALL dependencies
  3. Initializes the app (without connecting to anything)
  4. Extracts OpenAPI spec via SwaggerModule.createDocument()
  5. Closes the app and returns the spec

This means your CI doesn't need service containers for Postgres, Redis, RabbitMQ, etc.