Zero-config Nx plugins for modern TypeScript tooling. Register one plugin and get typecheck, test, lint, format, and build targets derived from the config files your project already keeps — no project.json, no target boilerplate.

Nx's project graph, caching, and affected detection are excellent; its built-in TypeScript tooling is not. nx-devkit keeps the graph and replaces the toolchain:

• tsdown instead of tsc emit for builds
• tsgo (@typescript/native-preview) for typecheck, with tsc fallback
• oxlint / ESLint / Biome for lint, Biome for format
• Vitest, or the native node --test runner when no Vitest config exists
• createNodesV2 inference — targets appear because tsconfig.json or biome.json exists, not because someone edited project.json

npx @nx-devkit/typescript init

In any workspace — Nx or plain TypeScript — this registers the preset in nx.json, detects your config files, installs missing tool dependencies, and prints the inferred targets. Works for single-package repos and monorepos.

Manual alternative:

bun add -D @nx-devkit/typescript   # or npm/pnpm/yarn add -D

// nx.json
{ "plugins": ["@nx-devkit/typescript"] }

The preset subsumes the standalone tsdown/oxlint/biome/vitest plugins; they stay available for single-tool consumers.

• Node.js ≥ 22.14 — the preset discovers configs with fs.globSync, which does not exist on older lines
• Nx ^22 || ^23 — installed automatically by init when missing
• Package manager — any of npm / pnpm / yarn / bun; binaries are resolved from node_modules/.bin
• Peer deps — typescript is the only required peer; @nx/devkit ships as a regular dependency (auto-installed, its own peer range carries the nx compatibility). Optional tool peers — vitest, oxlint, eslint, @biomejs/biome, tsdown: install only what your configs imply. @typescript/native-preview (tsgo) is optional and undeclared — add it for faster typecheck. init installs whatever is missing for the configs it detects.

All @nx-devkit/* packages are pre-1.0: minor versions may add or change inferred targets and option defaults; patches are fixes only. Check per-package CHANGELOG.md files before upgrading, and pin exact versions if your CI needs reproducible graphs.

What 1.0 means here. A package graduates to 1.0 when all of these hold:

• Inferred contract frozen — target names, inputs/outputs, and dependsOn wiring stop changing in minor versions (new targets may still be added).
• Options schema frozen — option renames/removals require a major bump; additions stay minor.
• Verified compat range — CI exercises the packed plugin against every supported Nx major (e2e-packed matrix), not just the newest.
• Naming settled — the packages/typescript-preset → @nx-devkit/typescript directory/package split is either accepted as documented or renamed once, before 1.0.
• Migrations shipped for breaks — any change that alters consumer nx.json or project layout comes with an nx migrate entry (the preset already ships migrations.json).

Use nx-devkit if your Nx workspace is a modern TypeScript toolchain and you want the project graph, caching, and affected without maintaining project.json targets per package — tsconfig.json, vitest.config.ts, biome.json, and friends are the project definition.

Stick with the official @nx/* plugins if you rely on their generators (library scaffolding, webpack/vite bundling configs) or need Jest/ESLint-specific Nx integrations beyond running the tools — nx-devkit deliberately replaces the toolchain layer, not the Nx ecosystem. It composes fine alongside official plugins: inference adds targets, it does not remove them.

A target I expected isn't showing up. Check what Nx inferred:

npx nx show project <name>          # lists every inferred target
npx nx reset && npx nx show projects  # clear the daemon cache, re-run inference

Inference is file-driven — the trigger config (vitest.config.*, .oxlintrc.*, …) must exist inside the project directory (root configs act as fallbacks for lint/format only). Enable verbose logging to see each decision:

NX_VERBOSE_LOGGING=true npx nx show projects   # or pass --verbose

lint ran the wrong tool. Lint has an explicit precedence: oxlint > eslint > biome, and each requires both its option enabled and its config present. oxlint: false hands lint to ESLint only when eslint: true and an eslint.config.* exists — otherwise Biome's fallback takes it. See the preset README.

command not found / binary resolution errors. Inferred targets call tool binaries from node_modules/.bin — the tool must be a devDependency somewhere reachable from the project root (hoisted installs work). Run npx @nx-devkit/typescript init to install the tools your configs imply.

The workspace root isn't a project. By design in monorepos: the root becomes a project only when it's the sole tsconfig. Force it either way with the includeRoot option.

Each plugin implements Nx's createNodesV2 API: during project-graph construction it globs for config files, then emits project nodes whose targets call the tool binaries — the same way Nx's own @nx/* plugins infer targets. Most targets are nx:run-commands (binaries resolved from node_modules/.bin, cwd = project root); the typecheck/build targets use dedicated executors that launch the tool's entry point directly (execFile/spawn, no shell), with walk-up node_modules resolution so hoisted monorepo installs work.

Because inference is per-run, the graph always reflects the files on disk: add vitest.config.ts and test appears. A single-package repo (a tsconfig at the root, none nested) gets a root project; the first nested tsconfig turns that off automatically — includeRoot on the preset forces the behavior either way.

MIT — see LICENSE.