Quality Gates

Block merges and deploys until lint, tests, typecheck, and security audit pass on Node.js 24 TypeScript code.

Recipe

Quick-reference recipe card - copy-paste ready.

steps:
  - run: npm ci
  - run: npm run lint
  - run: npm run typecheck
  - run: npm run test
  - run: npm audit --audit-level=high
  - run: npm run build

When to reach for this: Before any deploy to staging or production. Quality gates are non-negotiable for production Node APIs.

Working Example

{
  "scripts": {
    "lint": "eslint src --max-warnings 0",
    "typecheck": "tsc -p tsconfig.json --noEmit",
    "test": "vitest run --coverage",
    "test:unit": "vitest run --project unit",
    "test:integration": "vitest run --project integration",
    "build": "tsc -p tsconfig.json",
    "audit:ci": "npm audit --audit-level=high",
    "gates": "npm run lint && npm run typecheck && npm run test && npm run audit:ci && npm run build"
  }
}

# .github/workflows/ci.yml (excerpt)
jobs:
  gates:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: "24"
          cache: npm
      - run: npm ci
      - run: npm run gates
 
  docker-scan:
    needs: gates
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: docker build -t api:ci .
      - uses: aquasecurity/trivy-action@master
        with:
          image-ref: api:ci
          severity: CRITICAL,HIGH
          exit-code: 1

What this demonstrates:

• Single gates script local developers run before push
• --max-warnings 0 treats lint warnings as failures
• Trivy scan on Docker image after application gates pass

Deep Dive

Gate Ordering and Cost

ESLint Gate

// eslint.config.js excerpt
export default [
  {
    rules: {
      "no-console": "error",
      "@typescript-eslint/no-floating-promises": "error",
    },
  },
];

Ban console.log in src/; use structured logging.

Typecheck Gate

{
  "scripts": {
    "typecheck": "tsc -p tsconfig.json --noEmit"
  }
}

Run in CI even if build emits types. --noEmit is faster for PR feedback.

Coverage Threshold (Optional)

// vitest.config.ts
export default {
  test: {
    coverage: {
      thresholds: {
        lines: 80,
        functions: 80,
        branches: 70,
      },
    },
  },
};

Start with diff coverage on changed files if full-repo thresholds are too harsh initially.

Branch Protection

Configure in GitHub:

• Require status check gates (and docker-scan for release branches)
• Require PR review
• Dismiss stale approvals on new commits

Gotchas

• npm audit noise on transitive deps - blocks every PR. Fix: audit-level=high, Renovate for bumps, or npm audit fix playbook.
• Skipping typecheck when build runs tsc - build may skip strict files. Fix: explicit typecheck job.
• Lint only changed files in CI - main branch drifts. Fix: lint entire src/ on every run (fast enough).
• Integration tests without service containers - flaky CI. Fix: postgres/redis service containers in workflow.
• Docker scan only on main - vulnerable Dockerfile on PR merges. Fix: scan on PR when Dockerfile changes.
• No lockfile - npm ci fails or audit is meaningless. Fix: enforce package-lock.json in repo.

Alternatives

FAQs

Related

• CI/CD Basics - pipeline structure
• GitHub Actions for Node - workflow wiring
• Typecheck in CI - TypeScript gates
• Linting Basics - ESLint setup
• CI/CD Best Practices - section checklist

External Related Links

• Node.js Best Practices (GitHub) - Curated production best practices.
• npm CLI Documentation - Official docs for the npm CLI.
• NodeSource Blog & Resources - Enterprise Node.js performance and security content.
• Node.js Design Patterns, 4th Edition - Production-grade application patterns.
• Node.js Cookbook, 5th Edition - Practical server-side recipes.

Stack versions: This page was written for Node.js 24.18.0 (Active LTS), npm 10+, TypeScript 5.6+, Express 5, Fastify 5, and NestJS 11.