ESLint and TSConfig Presets

Use Nova Presets to lock in strict TypeScript, consistent style, and predictable builds. Pick the layers that match your stack.

Each preset is an ESM module designed for modern workspaces.

Install

If the package is not in your repo yet, go to Setup and Configure and choose Install into project.

ESLint Presets

Configure ESLint by composing small layers into a single flat config export. The goal is clear rules, low noise, and fast composition.

ESLint preset configurations and rule implementations are separate on purpose. Presets compose curated ESLint behavior, including novaRules, which registers Nova-owned rules and enables all of their scaffold defaults. Individual rule implementations remain available from @cbnventures/nova/rules/eslint. Consumers can append a later config object to change or disable any rule.

Mental Model

Nova's ESLint presets are flat config layers that you spread into one export. Think of them as small building blocks.

Each layer states intent and adds a focused set of opinions without hiding magic.

Composition follows a simple order:

1. Start with an ignores file to keep noise out.
2. Apply strict code styling so formatting is consistent project-wide.
3. Add a single language layer for the code you write (e.g., TypeScript).
4. Then the environment (runtime) or framework that matches where it runs.
5. Optionally, pick a platform.
6. Finish with any tool specifics.
7. Add novaRules, then append consumer-owned overrides last.

Available ESLint Presets

60-Second Setup

This example shows a minimal Node.js project using TypeScript, composed with Nova's ESLint presets. Configured through the eslint.config.mts file.

import {
  dxCodeStyle,
  dxIgnore,
  langTypescript,
  novaRules,
  runtimeNode,
} from '@cbnventures/nova/presets/eslint';

export default [
  ...dxIgnore,
  ...dxCodeStyle,
  ...langTypescript,
  ...runtimeNode,
  ...novaRules,
];

Read next: ESLint Best Practices.

TSConfig Presets

Configure TypeScript by chaining a few preset configs with "extends". Aim for consistent compiler behavior, strict typing, and predictable output with minimal overrides.

Mental Model

Nova's TSConfig presets are small layers you chain with "extends".

Composition follows a simple order:

1. Start with essentials as the baseline.
2. Apply strict for stronger compiler checks.
3. Select one role to decide whether TypeScript emits source, declarations, or nothing.
4. Add the runtime that matches where the code runs.
5. Add a framework when the project uses one.
6. Finish with any tool specifics.
7. Keep project paths, ambient types, includes, excludes, and output directories local.

The presets set the heavy knobs for you (e.g., module with moduleResolution, matching lib sets, etc.), so your config stays simple.

Keep local overrides focused on project wiring: paths for imports, outDir and rootDir for layout, types for type packages, and use include for the files you compile and exclude for build artifacts and node_modules.

Available TSConfig Presets

60-Second Setup

This example shows a minimal Node.js project using TypeScript, composed with Nova's TSConfig presets. Configured through the tsconfig.json file.

{
  "extends": [
    "@cbnventures/nova/presets/tsconfig/dx-essentials.json",
    "@cbnventures/nova/presets/tsconfig/dx-strict.json",
    "@cbnventures/nova/presets/tsconfig/role-source.json",
    "@cbnventures/nova/presets/tsconfig/runtime-node.json"
  ],
  "compilerOptions": {
    "outDir": "./build",
    "paths": {
      "@/*": [
        "./src/*"
      ]
    },
    "rootDir": "./",
    "types": [
      "@types/node"
    ]
  },
  "include": [
    "./*",
    "./src/**/*"
  ],
  "exclude": [
    "./build/**",
    "./node_modules/**"
  ]
}

Read next: TypeScript Compatibility and TSConfig Best Practices.

Scaffold Coverage

Every generated monorepo root has ESLint, TSConfig, and Vitest, even when it starts with no workspace. Every JavaScript or TypeScript workspace starts with dxIgnore, dxCodeStyle, dx-essentials, and dx-strict, enables novaRules, and includes a Vitest suite. Native-only workspace code keeps its native toolchain; Nova applies the JavaScript stack only to Node.js helpers that Nova generates.

Looking for individual custom ESLint rules and their options? See Nova Rules.