Issues

angular-rspack: AngularSsrDevServer process killed/spawned incrementally per each rebuild

Bug

nrwl/nx#37587 · opened

on Oct 25, 2026

angular-rspack: changes to server-only code not reflected in watched SSR build

Bug

nrwl/nx#37586 · opened

on Oct 25, 2026

Project graph: member calls named `import` / `require` are detected as module imports (and resolve differently on case-insensitive file systems)

nrwl/nx#37581 · opened

on Oct 24, 2026

1

nx release: independent project bumped via a non-releasable dependency gets an empty changelog ("version bump only")

Bug

nrwl/nx#37575 · opened

on Oct 23, 2026

nx login says "Already logged in" when the stored Nx Cloud OAuth login is expired and can't be refreshed

nrwl/nx#37513 · opened

on Oct 20, 2026

Could not find runner configuration for default on Node 22.18.0: real error is `conditions.has` is not a function, swallowed by a bare catch in getRunner

Bug

nrwl/nx#37502 · opened

on Oct 20, 2026

enforce-module-boundaries: banTransitiveDependencies reports packages whose "exports" omit package.json as unresolvable on Linux/macOS, not on Windows

nrwl/nx#37488 · opened

on Oct 19, 2026

Optimization: read compiler options without listing tsconfig files

nrwl/nx#37482 · opened

on Oct 19, 2026

4

Task-level affected: targets that aggregate other targets are never selected when their dependencies are affected

Bug

nrwl/nx#37479 · opened

on Oct 19, 2026

2

`nx reset` deletes the whole `cacheDirectory`, along with files Nx did not put there

nrwl/nx#37467 · opened

on Oct 17, 2026

A cache hit deletes git-tracked files under an output directory that the cache entry does not hold

nrwl/nx#37466 · opened

on Oct 17, 2026

Edits under a project's own `.nx/cache`, `.nx/workspace-data` or `.yarn/cache` directory never invalidate the cache

nrwl/nx#37465 · opened

on Oct 17, 2026

--exclude-task-dependencies caches the task under the full-graph hash, so a later full run restores output built from stale dependency files

nrwl/nx#37463 · opened

on Oct 17, 2026

An input edited while its target runs is cached under the old hash, so reverting the edit replays the newer output

nrwl/nx#37462 · opened

on Oct 17, 2026

Without the daemon, an input edited to new bytes of the same size and mtime replays the old outputs

nrwl/nx#37461 · opened

on Oct 17, 2026

Editing the file a symlinked input points to replays the old outputs until .nx/workspace-data is cleared

nrwl/nx#37460 · opened

on Oct 17, 2026

Changing only a file's executable bit keeps the task hash, so the old outputs are restored

nrwl/nx#37459 · opened

on Oct 17, 2026

A patched dependency (Yarn `patch:`, Bun `patchedDependencies`) does not change the task hash

nrwl/nx#37458 · opened

on Oct 17, 2026

Changing a package.json script's body replays the old output when the target sets its own inputs

nrwl/nx#37457 · opened

on Oct 17, 2026

A cross-project `dependsOn` target does not enter the task hash: editing it replays the old output

nrwl/nx#37456 · opened

on Oct 17, 2026

run-commands: fast-exiting task loses its output when stdout is not a TTY

nrwl/nx#37452 · opened

on Oct 17, 2026

`@nx/workspace:move` does not update `dependsOn` entries

Bug

nrwl/nx#37449 · opened

on Oct 17, 2026

`nx run` crashes with "No such device or address" if stdin is not a tty, stdout is a tty, and there is no controlling terminal

Bug

nrwl/nx#37447 · opened

on Oct 16, 2026

Editing and committing a tracked file under `outputs` gives a stale cache hit that restores the old bytes

nrwl/nx#37441 · opened

on Oct 16, 2026

Edits inside a symlinked directory input don't change the task hash (stale cache hit)

nrwl/nx#37440 · opened

on Oct 16, 2026

Navigation Menu

Repository navigation

Issues

angular-rspack: AngularSsrDevServer process killed/spawned incrementally per each rebuild

angular-rspack: changes to server-only code not reflected in watched SSR build

Project graph: member calls named `import` / `require` are detected as module imports (and resolve differently on case-insensitive file systems)

nx release: independent project bumped via a non-releasable dependency gets an empty changelog ("version bump only")

nx login says "Already logged in" when the stored Nx Cloud OAuth login is expired and can't be refreshed

Could not find runner configuration for default on Node 22.18.0: real error is `conditions.has` is not a function, swallowed by a bare catch in getRunner

enforce-module-boundaries: banTransitiveDependencies reports packages whose "exports" omit package.json as unresolvable on Linux/macOS, not on Windows

Optimization: read compiler options without listing tsconfig files

Task-level affected: targets that aggregate other targets are never selected when their dependencies are affected

`nx reset` deletes the whole `cacheDirectory`, along with files Nx did not put there

A cache hit deletes git-tracked files under an output directory that the cache entry does not hold

Edits under a project's own `.nx/cache`, `.nx/workspace-data` or `.yarn/cache` directory never invalidate the cache

--exclude-task-dependencies caches the task under the full-graph hash, so a later full run restores output built from stale dependency files

An input edited while its target runs is cached under the old hash, so reverting the edit replays the newer output

Without the daemon, an input edited to new bytes of the same size and mtime replays the old outputs

Editing the file a symlinked input points to replays the old outputs until .nx/workspace-data is cleared

Changing only a file's executable bit keeps the task hash, so the old outputs are restored

A patched dependency (Yarn `patch:`, Bun `patchedDependencies`) does not change the task hash

Changing a package.json script's body replays the old output when the target sets its own inputs

A cross-project `dependsOn` target does not enter the task hash: editing it replays the old output

run-commands: fast-exiting task loses its output when stdout is not a TTY

`@nx/workspace:move` does not update `dependsOn` entries

`nx run` crashes with "No such device or address" if stdin is not a tty, stdout is a tty, and there is no controlling terminal

Editing and committing a tracked file under `outputs` gives a stale cache hit that restores the old bytes

Edits inside a symlinked directory input don't change the task hash (stale cache hit)