Tags · nrwl/nx

23.2.0-beta.3

fix(js): resolve package and extension-less tsconfig extends read fro…

…m the tree (#36271)

## Current Behavior

Generators and migrations that parse a `tsconfig.json` from the devkit
`Tree` each build their own host that reads file contents from the
`Tree` but resolves file existence and paths through `ts.sys`. That host
cannot follow two `extends` forms:

- A package-provided base such as `@tsconfig/node20/tsconfig.json`.
TypeScript resolves it to an absolute path, which the `Tree` re-roots
under the workspace, so the base reads as nothing.
- An extension-less base such as `./tsconfig`. It resolves against the
current working directory, so it only works when the command runs from
the workspace root.

In both cases the base's options silently vanish from the merged result
(the failure surfaces only as a `TS5083`/`TS6053` the callers discard).
The `add-ignore-deprecations` TypeScript 6 migration can then miss a
deprecated option a config inherits from such a base, and generators can
read the wrong compiler options.

## Expected Behavior

`extends` resolves the way `tsc` resolves it, regardless of the
`extends` form or the working directory, when a config is parsed from
the `Tree`. A config that inherits a deprecated option through a package
or extension-less base is handled correctly by the TypeScript 6
migration, and generators read the fully-merged compiler options.

## Implementation Details

A single tree-faithful host, `createTreeParseConfigHost`, is extracted
into `@nx/js` and adopted at the five sites that each rebuilt one: the
angular and js tsconfig utilities, the js `setup-build` and rollup
`configuration` generators, and the `update-23-1-0`
`add-ignore-deprecations` TypeScript 6 migration. It maps absolute paths
under the `Tree` root back to tree-relative, falls back to `fs` for
paths that resolve outside the workspace (a pnpm store or a
`link:`/`file:` target), and answers existence from the `Tree`.
`realpath` and `getCurrentDirectory` are anchored to the `Tree` root, so
resolution is independent of the working directory: TypeScript resolves
a package-form base as a relative path and hands it to `realpath`, which
`ts.sys` would re-anchor to `process.cwd()`. The out-of-root `fs` branch
is gated on `isFile` to match `ts.sys`, so a directory is never read as
a config file.

The migration now warns about a config whose `extends` chain is
genuinely unresolvable instead of silently guessing at incomplete
options.

Two changes worth calling out: existence at the generator sites now
comes from the `Tree` rather than disk, so a base present on disk but
deleted in the `Tree` is reported unresolvable; and `readTsConfig`'s
optional `sys` parameter widens from `ts.System` to
`ts.ParseConfigHost`, a public `@nx/js` signature change that stays
source-compatible for existing callers.

Host unit tests and package-form and extension-less `extends` fixtures
are added to the migration spec.

## Related Issue(s)

Fixes NXC-4609

---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/nxc-4609-a2099980)

Jul 28, 2026
26fd7d9
zip
tar.gz
Notes

23.2.0-beta.2

fix(core): strip terminal query sequences when replaying task output (#…

…36432)

## Current Behavior

When a task's captured pty output is replayed (TUI summary, static
terminal output, cache replays), any terminal *query* escape sequences
the child emitted are written to the real terminal verbatim. The
terminal dutifully replies on stdin — but by then nx has restored cooked
mode and nothing is consuming replies, so the reply gets echoed into the
visible output as garbage next to the run summary, e.g.:

```
> nvim

^[[?62;22;52c
 NX   Successfully ran target edit for project @nx/nx-source (3m)
```

`ESC[?62;22;52c` is the terminal's Primary Device Attributes reply to
the `ESC[c` probe nvim sends at startup. The existing passthrough filter
only handles one such sequence (`ESC[6n`), fixing a single symptom
rather than the class.

## Expected Behavior

Replayed output is a recording — no process is waiting for the
terminal's answers anymore, so reply-eliciting sequences are stripped
before the replay is written. A new `stripTerminalQueries()` helper
removes:

- DA1/DA2/DA3 device attribute queries (`CSI c`, `CSI > c`, `CSI = c`) —
replies (`CSI ? … c`) are intentionally preserved
- DSR status/cursor reports (`CSI 5 n`, `CSI 6 n`, `CSI ? Ps n`)
- XTVERSION (`CSI > q`) and DECRQM mode queries (`CSI ? Ps $ p`)
- kitty keyboard protocol query (`CSI ? u`)
- XTWINOPS report requests (`CSI 14 t`, `CSI 18 t`, …) while preserving
non-reporting window ops
- OSC color/clipboard queries (`OSC 10;?`, `OSC 52;c;?`, …) while
preserving OSC sets like window titles
- XTGETTCAP / DECRQSS (`DCS + q … ST`, `DCS $ q … ST`)

The strip is applied in `output.logCommandOutput`, which every replay
path (tui-summary, static run-one/run-many, empty, invoke-runner life
cycles) funnels through. Live pty passthrough is untouched: while a task
runs, queries must reach the real terminal and the replies are consumed
in raw mode.

## Related Issue(s)

N/A — reported while testing #36322 locally; reproduced on stock nx
22.4.1, pre-existing and unrelated to that PR.

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Strip-terminal-query-sequences-from-replayed-task-output-895a849d)
<!-- polygraph-session-end -->

Jul 21, 2026
41d3bd4
zip
tar.gz
Notes

23.2.0-beta.1

fix(core): render critical-path tasks as a nested list in the job sum…

…mary (#36394)

## Current Behavior

In the GitHub Actions job summary, the Nx Run Report's "Speed up or
split the longest tasks on the critical path" recommendation renders its
task list as terminal-style rows collapsed with `<br>`:

```
- Speed up or split the longest tasks on the critical path:<br>e2e-react-native:e2e-macos-local                 20m 2s<br>@nx/nx-source:populate-local-registry-storage    5m 31s
```

The rows are space-padded for terminal column alignment, but HTML
collapses runs of spaces, so the rendered summary shows ragged,
hard-to-read lines jammed into a single bullet.

## Expected Behavior

The Markdown renderer formats the task list as a nested list under the
recommendation's bullet:

```
- Speed up or split the longest tasks on the critical path:
  - `e2e-react-native:e2e-macos-local` — 20m 2s
  - `@nx/nx-source:populate-local-registry-storage` — 5m 31s
```

Structurally, the critical-path recommendation now carries its task rows
as data (`RecTaskRows`) instead of a pre-joined terminal string, and
each renderer formats them natively. The terminal report and the TUI
popup payload output are byte-for-byte unchanged (covered by the
existing tests, which pass unmodified); only the job-summary Markdown
changes.

## Related Issue(s)

N/A

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Speed-up-main-macos-CI-job-parallel-e2e--drop-dead-Homebrew-cache-7918829a)
<!-- polygraph-session-end -->

---------

Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>

Jul 20, 2026
5c4419a
zip
tar.gz
Notes

23.2.0-beta.0

feat(core): add a full-width TUI status bar and vim-style pane search (…

…#36263)

## Current Behavior

The TUI task list renders its own bottom rows (keyboard hints, Nx Cloud
message, filter display) inside its own column, so they are cramped in
split layouts and disappear entirely when the task list is hidden
(fullscreen pane). The run title and NX badge live in the task-list
table header, terminal panes draw their own keybinding hints on their
bottom borders, and there is no way to search a pane's output. Much of
the UI state (cloud message/link, filter text, perf-report flag) is
duplicated between `TuiState` and `TasksList`, kept in sync via
broadcast actions.

## Expected Behavior

**Full-width status bar** on the bottom row of the TUI:

- Left: minimal progress counts with a live overall run duration —
`63/174 (1m 23s)` — which double as the clickable Nx Cloud link when a
structured link exists.
- Middle: free-text cloud messages (they can carry errors), transient
pane feedback ("copied to clipboard"), or the compact confirmed-search
display.
- Right: context-aware keyboard hints (task-list vs focused-pane) with
progressive fitting — as many whole hint items as fit the space — and
the `NON-INTERACTIVE i to toggle` / `INTERACTIVE <ctrl>+z to toggle`
indicator pinned right-most, never dropped.
- The task-list filter (`/`) swaps the bar row vim-style while typing;
the bar is mouse-selectable (drag to highlight + copy) and always
visible, including fullscreen-pane mode.
- The ` NX ` badge (run-state colored) and the run title stay at the
top-left of the task list in a minimal form; both columns keep
bottom-aligned scrollbars.

**Vim-style pane search**: `/` in a non-interactive pane searches the
full scrollback (case-insensitive, wrap-aware) with incremental jumping
while typing; Enter confirms into `n`/`N` navigation with wrap-around;
Esc cancels/clears. Matches highlight reverse-video with the current
match on a warning-colored background, and the bar shows `/query 2/5
(n/N)` while a confirmed search is active.

**State consolidation (started)**: `TuiState` is now the single owner of
the cloud message/link, filter text, and perf-report flag — the
`TasksList` mirrors and the `UpdateCloudMessage`/`UpdateCloudLink`
actions are deleted, and filter persistence across TUI mode switches is
automatic. Remaining mirrors (task statuses/timings, focus, pinned
tasks) are named follow-ups.

## Related Issue(s)


[NXC-4610](https://linear.app/nxdev/issue/NXC-4610/tui-full-width-status-bar-and-vim-style-terminal-pane-search)

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/TUI-Status-Bar-Development-11a216a4)
<!-- polygraph-session-end -->

Jul 17, 2026
ee5de80
zip
tar.gz
Notes

23.1.0

chore(repo): migrate to nx 23.1.0-rc.3 (#36321)

Jul 13, 2026
a5b10cd
zip
tar.gz
Notes

23.1.0-rc.3

fix(testing): template the e2e config for fresh projects instead of a…

…st-parsing it (#36304)

## Current Behavior

`@nx/cypress`'s e2e configuration generator scaffolds a `cypress.config`
from a base template (`defineConfig({})`), reads it back, and uses
`@phenomnomnominal/tsquery` to inject the `e2e` block. Loading tsquery
reads `ts.SyntaxKind` at import time. When a workspace resolves an
incompatible TypeScript — e.g. `npm install` hoisting `typescript@7` to
satisfy tsquery's unbounded `>3.0.0` peer in a workspace that pins no
TypeScript — that read throws:

```
 NX   Cannot convert undefined or null to object
    at Object.keys (<anonymous>)
    at .../@phenomnomnominal/tsquery/dist/src/syntax-kind.js
```

…and app generation fails. This is what crashes `e2e-expo` /
`e2e-react-native` (and any cypress-scaffolded app) on the macOS CI job,
which installs test workspaces with npm. The bare `apps` workspace pins
no TypeScript, so npm hoists TS 7 for tsquery's peer.

## Expected Behavior

For a freshly generated config the AST round-trip is unnecessary: nx
just wrote the empty base and knows every value going in (the module
shape was already decided when the base template was selected). The
generator now templates the complete `cypress.config` directly via a new
`buildE2EConfigFromBase` (no tsquery), so generation never loads tsquery
and no longer depends on the resolved TypeScript version.

The AST-based `addDefaultE2EConfig` is kept for the case that genuinely
needs it — merging the e2e config into a **pre-existing, possibly
user-authored** config (`nx g @nx/cypress:configuration` on a project
that already has a config). The templated output is **byte-identical**
to the previous AST output, so generated files and snapshots are
unchanged.

Verified: 227 cypress unit tests pass, 41 config snapshots unchanged,
and `e2e-expo:e2e-macos-local` passes under npm with **zero** tsquery
crashes (was 53).

## Related Issue(s)

Surfaced by the macOS e2e (`e2e-expo` / `e2e-react-native`) crashing
once TypeScript 7 was published to npm — cypress config generation
loaded tsquery, which reads the top-level `SyntaxKind` export that TS 7
removed.

<!-- polygraph-session-start -->
---
[View session information
↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/Migrate-nrwl-repos-to-nx-23.1.0-rc.0-b8c94700)
<!-- polygraph-session-end -->

Jul 13, 2026
74d5440
zip
tar.gz
Notes

PreviousNext

Navigation Menu

Uh oh!

23.2.0-beta.5

23.2.0-beta.4

23.1.1

22.7.8