Comparing changes

…project (#32073) Fixes #32069      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: Colum Ferry <cferry09@gmail.com> (cherry picked from commit af003c1)

update claude/agent.md with info about how to use docs (cherry picked from commit db33a7b)

…3885) When using `@nx/node:library` generator with `--compiler=swc`, the generator was incorrectly adding `tslib` as a dependency instead of `@swc/helpers`. This change fixes two issues: 1. Pass the correct bundler (matching the compiler) to jsLibraryGenerator so it adds the correct helper dependency to the project's package.json 2. Update ensureDependencies to only add tslib when compiler is tsc Fixes #31202 (cherry picked from commit 3db0fb2)

(cherry picked from commit 497345a)

## Expected Behavior  Update references to disablement variable for metrics collection for Nx Cloud enterprise users. --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> (cherry picked from commit 4931fbf)

## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # (cherry picked from commit e7758aa)

(cherry picked from commit 80501c9)

use astro-docs/src/content/approved-community-plugins.json instead. Fixes DOC-363 --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com> (cherry picked from commit 7d1ea67)

…isabled (#33881) ## Current Behavior When `NX_NATIVE_COMMAND_RUNNER=false` is set, tasks running in the TUI don't display any output in the terminal pane. The pane remains empty even though the task is running. ## Expected Behavior Task output is displayed in the TUI terminal pane regardless of the `NX_NATIVE_COMMAND_RUNNER` setting. ## Related Issues Fixes #32803 (cherry picked from commit d61ae25)

## Current Behavior The e2e test `should emit decorator metadata when using --compiler=swc` fails because the regex `/Foo=.*?_decorate/` expects the old transpiled output format where classes were assigned to variables. ## Expected Behavior The test should pass by matching the current SWC output format which uses native ES class syntax. ## Solution Updated the regex from `/Foo=.*?_decorate/` to `/class Foo.*_ts_metadata/` which: - Matches `class Foo` (native ES class syntax) - Verifies `_ts_metadata` is present (decorator metadata) (cherry picked from commit 4ebbe97)

…#33863) ## Current Behavior The same task can be pinned in multiple terminal panes of the TUI. This causes one pane to scroll the other because they share the same data. ## Expected Behavior The same task can only be pinned in a single terminal pane of the TUI. (cherry picked from commit 035e0fd)

@jason

The `argv` field was already implemented in `PreTasksExecutionContext` and `PostTasksExecutionContext` but lacked tests and documentation for plugin authors to discover and use it. ## Changes - **Added unit tests** (`packages/nx/src/daemon/server/handle-tasks-execution-hooks.spec.ts`) validating that `argv` flows correctly through hook handlers for different command patterns (direct, affected, run-many) - **Enhanced existing documentation** in `astro-docs/src/content/docs/extending-nx/task-running-lifecycle.mdoc` with a new section covering: - Context property definitions showing the `argv` field - Examples showing how to detect command types (direct execution, affected, run-many) - Example demonstrating conditional analytics based on the original command - Common command patterns reference - Best practices for defensive argv parsing ## Usage ```typescript import type { NxPlugin, PostTasksExecutionContext } from '@nx/devkit'; export const myPlugin: NxPlugin = { name: 'my-plugin', postTasksExecution: async (options, context: PostTasksExecutionContext) => { // Distinguish between nx build my-app vs nx affected -t build if (context.argv.includes('affected')) { console.log('Running in affected mode'); } } }; ``` Fixes https://linear.app/nxdev/issue/NXC-3382/add-contextargv-to-task-execution-hook-contexts  <details> <summary>Original prompt</summary> > Issue Title: Add context.argv to task execution hook contexts > Issue Description: Expose the original CLI arguments on the plugin worker so hooks can distinguish how execution was started (e.g., `nx build nx-api` vs `nx affected -t build`). Proposal: include the invoking argv on the hook context (e.g., `context.argv`). > Fixes https://linear.app/nxdev/issue/NXC-3382/add-contextargv-to-task-execution-hook-contexts > > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > [https://github.com/nrwl/nx](https://github.com/nrwl/nx) > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Aha! that worked - so you can tell it to assign to copilot instead of "me and copilot" > > Comment by User d484ef82-7f7d-4a95-be09-9d82ca3905dc: > 📋 I wasn't able to determine which GitHub repository to work in. > > I think it's one of these, but can you tell me which one is right? > > Comment by User : > Created issue [NXC-3382](https://linear.app/nxdev/issue/NXC-3382/add-contextargv-to-task-execution-hook-contexts) > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > This comment thread is synced to a corresponding [thread in Slack](https://nrwl.slack.com/archives/C070BJ2JYLW/p1761928859857989?thread_ts=1761928859.857989&cid=C070BJ2JYLW). All replies are displayed in both locations. > > Comment by User : > This thread is for an agent session with githubcopilot. > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > @linear make a ticket and assign it to copilot > > Comment by User f5ae6d50-28e9-4ee7-ad51-3da8208d5914: > Makes sense to me > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Sure, context.argv? > > Comment by User f5ae6d50-28e9-4ee7-ad51-3da8208d5914: > We can add them as `argv`? > > Comment by User f5ae6d50-28e9-4ee7-ad51-3da8208d5914: > Yeah they would run on the plugin worker so it's not there > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > @jason we could add `originalArgv` to the contexts? > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Eh, probably not... they run on the plugin worker > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Yeah, I don't think the hooks know.... I'd be curious if process.argv would just have that info though > > Comment by User 439b15a6-827b-4258-971a-d86133ad59de: > payfit does > > Comment by User 74901385-a023-4825-8470-fe68b1b55664: > I can’t see anything about that in the docs - so I would assume the hooks are agnostic to how the tasks were triggered? > > Comment by User 74901385-a023-4825-8470-fe68b1b55664: > so they’re asking is there’s a way to tell the difference between `nx build nx-api` or `nx affected -t build` in the task hook? > > Comment by User 74901385-a023-4825-8470-fe68b1b55664: > > I’ve been playing around with the Task Execution Hooks, specifically the postTasksExecution hook, and I think it will be really useful for me to grab some detailed metrics for our specific use cases. > > What I feel like it’s missing is a way to see what command actually started the task execution, whether it was a specific target or an affected command. As long as it was a specific target, I think the tasks are sorted in order so the last taskResult will probably be the actual target of the command but for affected it seems a bit more random what the last result will be. > > Is there a way to know exactly which command kicked off the ‘task execution’? > > </details>  --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: AgentEnder <6933928+AgentEnder@users.noreply.github.com> Co-authored-by: Craigory Coppola <craigorycoppola@gmail.com> Co-authored-by: Caleb Ukle <caleb@nrwl.io> Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: Copilot <Copilot@users.noreply.github.com> (cherry picked from commit ffc5f69)

…ng data (#33887) This PR adds a validation to the directory prompt, so users should not hit the error as often. Only possible now if they pass the arg from CLI _and_ they are in non-interactive mode. We also added some more data to help debug problems, such as node version, template/preset chosen, etc. And updated the message in "custom" preset prompt to align with the more effective "full platform" prompt. Note: Also update the error message (if it hits) to be the same in new flow and old flow. ## Related Issue(s) Closes NXC-3624 --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> (cherry picked from commit cf7ecc9)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comparing changes

Open a pull request

Commits on Dec 16, 2025

This comparison is taking too long to generate.

Uh oh!