Post

🚀 Nx 23.3 is out. - Task-based nx affected - Agent-friendly task output - Batched Oxlint runs - Faster project graph creation - Cypress 16, Vitest 5, pnpm 12 And more. All the details 👇 nx.dev/blog/nx-23-...

nx.devNx 23.3 Is Here: Task-Based Affected, Faster Graph Creation and Agent-Friendly Output | Nx BlogNx 23.3 selects affected tasks instead of whole projects, builds the project graph faster on large repos, and gets ready for Nx 24.

@nx.dev

Until now, nx affected worked at the project level. Change one spec file in a shared library and every project depending on it is affected too. 23.3 selects tasks by what they read, so that change only runs the test task of the project the spec file lives in.

8/10/26, 2:53 pm0 reposts1 like

@nx.dev

Task-based affected is opt-in in 23.3 and we plan to make it the default in Nx 24: NX_LEGACY_AFFECTED=false nx affected -t test If a task shows up (or doesn't) and you're not sure why, add --explain. It lists the affected tasks and exits without running anything.

@nx.dev

The Oxlint plugin we shipped in 23.2 now runs in batch mode by default. Nx starts a single Oxlint process for all projects, and each project still keeps its own result, logs and cache entry. On a workspace with 50 libraries, linting went from 16.5s to 3.0s.

@nx.dev

When an AI agent runs Nx, it now gets the new summary output style by default. Nx prints the task counts and, for each failed task, the path to its full log. The agent reads a log file only when it needs the details, which keeps the token usage low.

@nx.dev

Project graph creation got up to 60% faster on cold runs and up to 80% faster on warm runs in a large enterprise workspace. How much you gain depends on your repo and the machine it runs on.