NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #3187 most downloaded on npm
The Nx Devkit is used to customize Nx for different technologies and use cases. It contains many utility functions for reading and writing files, updating configuration, working with Abstract Syntax Trees(ASTs), and more. Learn more about [extending Nx by
Latest stable
24.0.6
Last release 8 days ago
14 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
1977 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
core: move @nx/conformance and @nx/owners into the nx repo
dependsOn entries in move generator (#37450, #37449)Your coding agent can read these notes before it upgrades. Set up the MCP server →
js: remove the deprecated classproperties babel preset option
core: keep run-commands output written right before a command exits ( #37762 , #37452 )
core: check ownership of daemon and pseudo-terminal socket directories
angular-rspack: respect component style minification ( #37722 , #37713 )
angular-rspack: print diagnostic positions and full warning text ( #37637 , #37431 )
angular: register the ssr dev server afterEmit hook only once ( #37589 , #37587 )
angular-rspack: install the plugin after Angular dependencies
⚠️ angular: remove deprecated SCAM generators
setParserOptionsProject generator option is
removed. Use enableTypedLinting instead. nx migrate rewrites
generator defaults that set it, but not scripts that pass
--setParserOptionsProject to nx g.NX_MIGRATE_SKIP_REGISTRY_FETCH is removed, and nx migrate ignores it. To keep resolving versions and migration metadata
through a package-manager install, set
NX_MIGRATE_USE_REGISTRY_RESOLUTION=false or
migrate.useRegistryResolution: false in nx.json.@nx/angular:scam, @nx/angular:scam-directive,
@nx/angular:scam-pipe, and @nx/angular:scam-to-standalone generators
and their @nx/angular/generators exports are removed. Use the
@nx/angular:component, @nx/angular:directive, or @nx/angular:pipe
generators instead.NX_ISOLATE_PLUGINS=false or NX_USE_V8_SERIALIZER=true, or that use
the WASM build of Nx. In those workspaces, a project whose project.json
has no name was named after its directory. It now gets the name Nx
already gives it with default settings. That name comes from its
package.json name, or from another plugin such as @nx/maven. For
example, packages/foo with the package name @scope/foo changes from
foo to @scope/foo. Update commands and configuration that use the
old name, such as nx build foo or implicitDependencies. To keep the
old name, set "name": "foo" in project.json.@nx/js/typescript is the only tsc typecheck
provider, in TS solution setups and outside them. @nx/rsbuild,
@nx/remix/plugin and @nx/react/router-plugin no longer infer a
typecheck target and drop typecheckTargetName. @nx/vite/plugin
infers one only for Vue projects (vue-tsc). Each package's 24.0.0
migration registers @nx/js/typescript where it's missing.@nx/dotnet no longer infers a restore target. Run
dotnet restore directly, or set "restore": true in the plugin's
options in nx.json.
Stacked on #36981, and aimed at the 24 train. The last commit is the new
work.outputs placeholder whose option is 0 or false resolves to
that value instead of dropping the output.{env.*} and ?? fallbacks in the release settings that resolve
placeholders, such as tag patterns and commit messages, are an error
instead of literal text. Docker versionSchemes, which @nx/docker
resolves, are unchanged.nx:run-commands, the default, builds the command env the
way forked mode does. envFile references see the project's .env
values, and an empty shell variable no longer overrides an envFile
value. NX_LOAD_DOT_ENV_FILES and the root .env follow the task env,
not the Nx process, except for a command in a pseudo-terminal (see
Implementation Notes).dependsOn entries with projects: 'self' or
projects: 'dependencies' are no longer special. Run nx repair to
rewrite them to the token form.nx watch --includeDependentProjects is removed. Use
--includeDependencies.October 21, 2026
24.0.6 24.0.5 24.0.4 24.0.3 24.0.2 24.0.1
Nx 24 comes with task-based affected, waitFor / readyWhen for continuous tasks, and refreshed Node.js apps. It removes the executors, generators and config helpers deprecated in Nx 23.
Task-based affected : nx affected -t selects tasks whose inputs your change touches. A PR that only edits a spec file runs the project's test but not its build . New workspaces get it by default. Upgrading sets affected.legacy: true , so existing workspaces keep project selection until you remove it ( migration ).
Wait for continuous tasks to be ready : a task can wait until a continuous task it depends on is ready, such as an e2e task waiting for the dev server to accept requests.
"dependsOn" : [ { "projects" : "shop" , "target" : "serve" , "waitFor" : "ready" } ]
The serve and dev targets of first-party plugins infer a readyWhen check. Write your own with url , port , command , logMatches or signal ( docs ). To have the server report the port it listens on, add nxReadySignal() (Vite) or pluginNxReadySignal() (Rsbuild). NxAppWebpackPlugin and NxAppRspackPlugin already report it; other webpack and Rspack configs add NxReadySignalPlugin . Inferred Cypress and Playwright e2e tasks wait when waitForServerReady is true , which the upgrade sets to false in existing workspaces.
Skip unaffected split e2e tests : a test file split by the Atomizer reruns only when the projects it names change ( docs ).
// apps/shop-e2e/src/checkout.spec.ts // @nx-depends-on: checkout
Refreshed Node.js apps : new apps build with tsc , or with the new @nx/rolldown plugin in workspaces that use path aliases. nx serve runs the source with node --watch . The new @nx/js/node plugin infers that task from the shebang in src/main.ts , and infers one for any other script with a node shebang ( docs ).
#!/usr/bin/env node // @nx-target-name: serve
Migrations in agents : inside an AI agent, nx migrate --run-migrations runs each migration as a resumable step and commits it.
Plugin performance : lower CPU and memory use during graph creation in @nx/rollup , @nx/vite , @nx/js/typescript , @nx/storybook , @nx/rspack and @nx/remix .
Maven and Gradle treat files under the build directory as build output, whatever .gitignore says, so cached test and package runs no longer restore stale classes.
nx run typos print "Did you mean" and the available targets.
Angular 22.2 support : nx migrate updates the Angular packages to 22.2. It skips workspaces that use Cypress component testing or webpack Module Federation in an Angular project, which break with the webpack versions Angular 22.2 installs.
Run nx migrate latest first. Most of these ship with a migration.
Task graph format : dependencies and continuousDependencies in the task graph hold edge objects instead of task IDs. Batch executors, executors that read context.taskGraph , and scripts that parse nx graph --file output read the edge's id . @nx/devkit exports the TaskGraphEdge type.
// before "dependencies" : { "shop:build" : [ "ui:build" ] } , "continuousDependencies" : { "shop-e2e:e2e" : [ "shop:serve" ] } // after "dependencies" : { "shop:build" : [ { "id" : "ui:build" } ] } , "continuousDependencies" : { "shop-e2e:e2e" : [ { "id" : "shop:serve" , "waitFor" : "ready" } ] }
On-prem Nx Cloud reads this graph for Nx Agents and distributed task execution. Update it to 2026.10.1 or later before you upgrade to Nx 24.
Deprecated executors removed : the 35 executors across 14 plugins deprecated in Nx 23 are gone, along with exported executor functions such as webpackExecutor . The migration converts their targets to inferred tasks and moves options into the tool's config file (e.g. webpack ). See Removed executors for the full list.
Generators always add inference plugins : the addPlugin option is removed, so generators register their plugin instead of writing executor targets. Remove addPlugin from code that calls them.
Removed generators : @nx/react:setup-ssr , and the Angular SCAM generators ( scam , scam-directive , scam-pipe , scam-to-standalone ). Use @nx/angular:component , directive or pipe instead.
Config helpers removed : composePlugins and withNx (webpack, Rspack, Next.js), withWeb and withReact (webpack, Rspack), and nxViteTsPaths and nxCopyAssetsPlugin (Vite). The migrations rewrite your configs (e.g. webpack config setup ).
// before module . exports = composePlugins ( withNx (), withReact ()); // after module . exports = { plugins : [ new NxAppWebpackPlugin ({ main : './src/main.tsx' }), new NxReactWebpackPlugin ()], };
Plugins no longer infer typecheck : @nx/vite/plugin (except Vue), @nx/rsbuild , @nx/remix/plugin and @nx/react/router-plugin . Only @nx/js/typescript infers it, and the migration registers it.
cache in target defaults : when an executor key and a target-name key both match a target, Nx no longer reads cache from the target-name key. Nx has warned about this since 23.2. Set cache on the executor key.
// before: build targets using @nx/angular:webpack-browser were cached through "build" "build" : { "cache" : true } , "@nx/angular:webpack-browser" : { "inputs" : [ "production" , "^production" ] } // after "@nx/angular:webpack-browser" : { "inputs" : [ "production" , "^production" ] , "cache" : true }
dependsOn : projects: 'self' and projects: 'dependencies' used to mean this project and its dependencies. Nx 24 reads them as project names. Run nx repair to rewrite them.
{ "projects" : "self" , "target" : "codegen" } // before { "target" : "codegen" } // after { "projects" : "dependencies" , "target" : "build" } // before { "dependencies" : true , "target" : "build" } // after
nx watch : --includeDependentProjects is removed. Use --includeDependencies .
nx:run-commands : direct mode, the default, now builds the env like forked mode, so envFile values read the project's .env instead of the root one. Given:
nx serve api now gets API_URL=http://localhost:5000 , matching the app's PORT . Before, direct mode gave it http://localhost:3000 from the root .env .
Nx Module Federation removed , including the React and Angular host and remote generators. See Migrate off @nx/module-federation .
Remix : @nx/remix is deprecated and goes away in Nx 25. Its generators and executors are removed, except convert-to-inferred . A migration moves apps to React Router v7.
Gradle : @nx/gradle/plugin-v1 is replaced with @nx/gradle , with a migration .
.NET : @nx/dotnet no longer infers restore . Replace nx run-many -t restore with dotnet restore .
createDependencies is no longer exported from @nx/vite/plugin , @nx/js/typescript , @nx/storybook/plugin , @nx/rspack/plugin and @nx/remix/plugin .
pnpm pruning fails when an app has its own file:workspace_modules/<name> dependency, which collides with the copied workspace library. Move that package to another folder ( docs ).
Project names : with NX_ISOLATE_PLUGINS=false , NX_USE_V8_SERIALIZER=true or the WASM build, a project.json without a name takes it from package.json .
Custom hashers on executors are deprecated and go away in Nx 25. A migration lists them.
@nx/playwright:wait-for-webserver is deprecated and goes away in Nx 25. Use waitFor: "ready" instead.
📄 Task-based affected
📄 Wait for a continuous task to be ready
📄 Skip unaffected split e2e tests
📄 Rolldown plugin
📄 Node.js
📄 Convert to inferred tasks
See the full Nx 24.0.0 release notes for the complete list.
js: read script shebangs natively and watch by default
⚠️ angular: remove deprecated SCAM generators
setParserOptionsProject generator option is
removed. Use enableTypedLinting instead. nx migrate rewrites
generator defaults that set it, but not scripts that pass
--setParserOptionsProject to nx g.NX_MIGRATE_SKIP_REGISTRY_FETCH is removed, and nx migrate ignores it. To keep resolving versions and migration metadata
through a package-manager install, set
NX_MIGRATE_USE_REGISTRY_RESOLUTION=false or
migrate.useRegistryResolution: false in nx.json.@nx/angular:scam, @nx/angular:scam-directive,
@nx/angular:scam-pipe, and @nx/angular:scam-to-standalone generators
and their @nx/angular/generators exports are removed. Use the
@nx/angular:component, @nx/angular:directive, or @nx/angular:pipe
generators instead.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
angular: support angular v22.2 (#37234, #37375)
NX_ISOLATE_PLUGINS=false or NX_USE_V8_SERIALIZER=true, or that use
the WASM build of Nx. In those workspaces, a project whose project.json
has no name was named after its directory. It now gets the name Nx
already gives it with default settings. That name comes from its
package.json name, or from another plugin such as @nx/maven. For
example, packages/foo with the package name @scope/foo changes from
foo to @scope/foo. Update commands and configuration that use the
old name, such as nx build foo or implicitDependencies. To keep the
old name, set "name": "foo" in project.json.misc: remove deprecated executors
@nx/js/typescript is the only tsc typecheck
provider, in TS solution setups and outside them. @nx/rsbuild,
@nx/remix/plugin and @nx/react/router-plugin no longer infer a
typecheck target and drop typecheckTargetName. @nx/vite/plugin
infers one only for Vue projects (vue-tsc). Each package's 24.0.0
migration registers @nx/js/typescript where it's missing.@nx/dotnet no longer infers a restore target. Run
dotnet restore directly, or set "restore": true in the plugin's
options in nx.json.
Stacked on #36981, and aimed at the 24 train. The last commit is the new
work.outputs placeholder whose option is 0 or false resolves to
that value instead of dropping the output.{env.*} and ?? fallbacks in the release settings that resolve
placeholders, such as tag patterns and commit messages, are an error
instead of literal text. Docker versionSchemes, which @nx/docker
resolves, are unchanged.nx:run-commands, the default, builds the command env the
way forked mode does. envFile references see the project's .env
values, and an empty shell variable no longer overrides an envFile
value. NX_LOAD_DOT_ENV_FILES and the root .env follow the task env,
not the Nx process, except for a command in a pseudo-terminal (see
Implementation Notes).core: keep always inputs under ultracache and scope e2e files with @nx-depends-on
core: own socket path resolution in the native crate
⚠️ core: remove deprecated nx watch --includeDependentProjects alias
dependsOn entries with projects: 'self' or
projects: 'dependencies' are no longer special. Run nx repair to
rewrite them to the token form.nx watch --includeDependentProjects is removed. Use
--includeDependencies.core: flush task output before the task process exits
vitest: allow vitest 5 when angular packages peer it ( #37394 , #37393 )
angular-rspack: update piscina to address critical vulnerability
October 7, 2026
23.3.2 23.3.1
23.3 adds task-based affected when running nx affected , and speeds up project graph creation on large repos.
Task-based affected : opt in with NX_LEGACY_AFFECTED=false and Nx runs only the tasks whose inputs your change reaches. --explain shows why each task was selected.
Faster project graph creation : up to 60% faster cold and 80% faster warm on a large enterprise workspace.
Batched Oxlint runs : the inferred lint target lints many projects in one Oxlint process while keeping per-project caching.
--output-style=summary prints task counts and a log path per failure instead of inlining logs, which keeps AI agent token use low. Nx uses it by default when it detects an agent.
Ecosystem updates : Vitest 5, Cypress 16, NgRx 22 and pnpm 12.
Watch the release video or read the full Nx 23.3 release post for the complete story.
Get ready for Nx 24
Nx 24 removes the built-in executors that have an inferred task replacement. Run npx nx g infer-targets to convert your projects to inferred tasks ahead of the upgrade.
📄 Task-based affected
📄 Gitignored files as task inputs
📄 Batched Oxlint runs
📄 Explain why tasks are affected
23.3 ships 90 fixes since 23.2.0. See the full Nx 23.3.0 release notes for the complete list.
core: stop merging declared negations into ultracache file groups
core: run a final agent validation pass at the end of an orchestrated migrate run
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
core: explain why each task is affected with --explain
One column per quarter.