Configuration

Configuration is optional. nestjs-doctor applies reasonable defaults when no configuration file is present.

Config File

Create nestjs-doctor.config.json in your project root:

{
  "minScore": 75,
  "ignore": {
    "rules": ["architecture/no-orm-in-services"],
    "files": ["src/generated/**"]
  },
  "rules": {
    "architecture/no-barrel-export-internals": false
  },
  "categories": {
    "performance": false
  }
}

Or use a "nestjs-doctor" key in package.json:

{
  "nestjs-doctor": {
    "minScore": 75,
    "rules": {
      "architecture/no-barrel-export-internals": false
    }
  }
}

Config Resolution

The config loader searches for configuration in this order:

1. Explicit path via --config flag
2. nestjs-doctor.config.json in the project root
3. .nestjs-doctor.json in the project root
4. "nestjs-doctor" key in package.json
5. Built-in defaults

The first match takes precedence. See Config Loading for implementation details.

Options

Rules can be set to false to disable them, or configured with an object to override severity:

{
  "rules": {
    "architecture/no-barrel-export-internals": false,
    "security/no-hardcoded-secret": { "enabled": true, "severity": "error" }
  }
}

Rule objects can also include rule-specific options. Example for no-manual-instantiation:

{
  "rules": {
    "architecture/no-manual-instantiation": {
      "excludeClasses": ["Logger", "PinoLogger"]
    }
  }
}

Default Excludes

These patterns are always excluded (your exclude config is additive):

• node_modules/**, dist/**, build/**, coverage/**
• **/*.spec.ts, **/*.test.ts, **/*.e2e-spec.ts, **/*.e2e-test.ts
• **/*.d.ts
• **/test/**, **/tests/**, **/__tests__/**
• **/__mocks__/**, **/__fixtures__/**, **/mock/**, **/mocks/**, **/*.mock.ts
• **/seeder/**, **/seeders/**, **/*.seed.ts, **/*.seeder.ts

Include vs Exclude Behavior

• exclude patterns are additive to defaults. Your patterns are appended, so safety exclusions like node_modules are never accidentally removed.
• include patterns replace defaults entirely. If you set include, only those patterns are scanned.

Monorepo Support

Monorepo mode is auto-detected using five strategies (checked in priority order — first match wins):

1. nest-cli.json (takes precedence)

{
  "monorepo": true,
  "projects": {
    "api": { "root": "apps/api" },
    "admin": { "root": "apps/admin" },
    "shared": { "root": "libs/shared" }
  }
}

2. pnpm-workspace.yaml (pnpm / Turborepo)

packages:
  - "apps/*"
  - "packages/*"

3. package.json workspaces (npm / Yarn)

Both array and object formats are supported. Skipped when pnpm-workspace.yaml exists.

{
  "workspaces": ["apps/*", "packages/*"]
}

4. nx.json (Nx)

Discovers sub-projects by scanning for project.json files alongside nx.json.

5. lerna.json (standalone Lerna)

Used when useWorkspaces is not set. Defaults to ["packages/*"] if no packages globs are specified. When useWorkspaces is true, detection falls through to strategy 3.

{
  "packages": ["packages/*"]
}

Non-NestJS packages are always filtered out — only packages with @nestjs/core or @nestjs/common are included. If a monorepo is detected but no NestJS packages are found, nestjs-doctor emits a warning and falls back to single-project mode.

Each sub-project is scanned independently. Per-project config files are supported — place a nestjs-doctor.config.json inside a sub-project's root to override the root config for that project.

The report shows a combined score plus a per-project breakdown.

Scoring

Scores are weighted by severity and category, normalized by file count:

See Scoring for the full formula and calibration details.