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

@gentleduck/gen

v0.2.7

Published

Type-safe API and message generator for TypeScript projects (NestJS-tested).

Readme

@gentleduck/gen

Duck Gen scans your TypeScript server code and generates type-safe route maps and message registries. It is currently tested with NestJS.

Install

pnpm add -D @gentleduck/gen

Quick start

Create a duck-gen.json at your project root:

{
  "$schema": "node_modules/@gentleduck/gen/duck-gen.schema.json",
  "framework": "nestjs",
  "extensions": {
    "shared": {
      "includeNodeModules": false,
      "outputSource": "./generated",
      "sourceGlobs": ["src/**/*.ts", "src/**/*.tsx"],
      "tsconfigPath": "./tsconfig.json"
    },
    "apiRoutes": {
      "enabled": true,
      "globalPrefix": "/api",
      "normalizeAnyToUnknown": true,
      "outputSource": ["./generated", "./src/generated"]
    },
    "messages": {
      "enabled": true,
      "outputSource": "./generated"
    }
  }
}

Add a message group tagged for Duck Gen:

/**
 * @duckgen messages
 */
export const AuthMessages = [
  'AUTH_SIGNIN_SUCCESS',
  'AUTH_SIGNIN_FAILED',
] as const

Run the generator:

pnpm exec duck-gen

Import generated types (package outputs only exist when you don't set outputSource):

import type {
  ApiRoutes,
  DuckGenI18nMessages,
  DuckgenScopedI18nByGroup,
} from '@gentleduck/gen/nestjs'

If you configure outputSource, import directly from your generated file instead:

import type { ApiRoutes } from './generated/duck-gen-api-routes'

Output

Duck Gen writes type definitions to @gentleduck/gen/generated/<framework> and exposes them via framework entrypoints like @gentleduck/gen/nestjs only when no output paths are configured. If you set extensions.shared.outputSource, extensions.apiRoutes.outputSource, or extensions.messages.outputSource, the generator writes only to those configured paths (paths resolve relative to duck-gen.json). When you customize outputs, import types from those files directly instead of the package entrypoints.

Generated files include:

  • duck-gen-api-routes.d.ts
  • duck-gen-messages.d.ts
  • index.d.ts

Notes

  • If duck-gen.json is missing, defaults are used.
  • Run the CLI from the project root so paths resolve correctly.
  • Message arrays should be as const so keys are literal types.
  • sourceGlobs are resolved relative to duck-gen.json and override tsconfig includes for that extension when provided.
  • If no sourceGlobs are provided, Duck Gen uses defaults:
    • API routes: **/*.controller.ts(x)
    • Messages: **/*.ts(x)
  • API routes do not fall back to extensions.shared.sourceGlobs. If your controllers don’t follow *.controller.ts(x), set extensions.apiRoutes.sourceGlobs explicitly.
  • Duck Gen automatically excludes node_modules, dist, generated, and .turbo from globs unless includeNodeModules is true.
  • If no tsconfigPath is set, Duck Gen prefers tsconfig.duckgen.json (if it exists) and falls back to tsconfig.json.