Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
1188
7a8a4d41 docs(nx): add --ignore-existing to all npx commands
53 minutes ago by Victor Savkin
Succeeded
master
e41ba65a fix(nx-cloud): download light client to tmp dir when outside nx workspace (#34805) ## Current Behavior When running nx commands outside of an Nx workspace (no nx.json), the light client is downloaded to .nx/cache/cloud relative to process.cwd(). This creates an unwanted .nx folder in whatever directory the user happens to be in. ## Expected Behavior When outside an Nx workspace, the light client is downloaded to a temp directory (os.tmpdir()/nx-cloud-client/hash) where hash is derived from the NX_CLOUD_API URL. This avoids polluting arbitrary directories with .nx folders while ensuring different cloud instances get separate directories. When inside an Nx workspace, behavior is unchanged.
2 hours ago by Victor Savkin
Succeeded
master
e41ba65a fix(nx-cloud): download light client to tmp dir when outside nx workspace (#34805) ## Current Behavior When running nx commands outside of an Nx workspace (no nx.json), the light client is downloaded to .nx/cache/cloud relative to process.cwd(). This creates an unwanted .nx folder in whatever directory the user happens to be in. ## Expected Behavior When outside an Nx workspace, the light client is downloaded to a temp directory (os.tmpdir()/nx-cloud-client/hash) where hash is derived from the NX_CLOUD_API URL. This avoids polluting arbitrary directories with .nx folders while ensuring different cloud instances get separate directories. When inside an Nx workspace, behavior is unchanged.
7 hours ago by Victor Savkin
Succeeded
master
e41ba65a fix(nx-cloud): download light client to tmp dir when outside nx workspace (#34805) ## Current Behavior When running nx commands outside of an Nx workspace (no nx.json), the light client is downloaded to .nx/cache/cloud relative to process.cwd(). This creates an unwanted .nx folder in whatever directory the user happens to be in. ## Expected Behavior When outside an Nx workspace, the light client is downloaded to a temp directory (os.tmpdir()/nx-cloud-client/hash) where hash is derived from the NX_CLOUD_API URL. This avoids polluting arbitrary directories with .nx folders while ensuring different cloud instances get separate directories. When inside an Nx workspace, behavior is unchanged.
8 hours ago by Victor Savkin
Succeeded
master
e41ba65a fix(nx-cloud): download light client to tmp dir when outside nx workspace (#34805) ## Current Behavior When running nx commands outside of an Nx workspace (no nx.json), the light client is downloaded to .nx/cache/cloud relative to process.cwd(). This creates an unwanted .nx folder in whatever directory the user happens to be in. ## Expected Behavior When outside an Nx workspace, the light client is downloaded to a temp directory (os.tmpdir()/nx-cloud-client/hash) where hash is derived from the NX_CLOUD_API URL. This avoids polluting arbitrary directories with .nx folders while ensuring different cloud instances get separate directories. When inside an Nx workspace, behavior is unchanged.
9 hours ago by Victor Savkin
Succeeded
master
6b8d5c9e fix(core): allow cloud commands to run via npx without local install Static imports of analytics and perf-logging modules introduced in recent PRs caused native Nx modules to load at file parse time, before the cloud command bypass logic could run. This broke `npx nx@latest polygraph`, `npx nx@latest login`, and other cloud commands when run without a local Nx installation. Move the cloud command check before analytics initialization and convert analytics/perf-logging to dynamic requires so they only load for non-cloud commands. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
9 hours ago by Victor Savkin
Succeeded
34865
Generating fix→
8eac526f fix(core): allow cloud commands to run via npx without local install Static imports of analytics and perf-logging modules introduced in recent PRs caused native Nx modules to load at file parse time, before the cloud command bypass logic could run. This broke `npx nx@latest polygraph`, `npx nx@latest login`, and other cloud commands when run without a local Nx installation. Move the cloud command check before analytics initialization and convert analytics/perf-logging to dynamic requires so they only load for non-cloud commands. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
9 hours ago by Victor Savkin
Succeeded
1186
20961db0 docs(nx): add nx in enterprises guide
13 hours ago by Victor Savkin
Succeeded
502
3f873f7c fix(schematics): skip projects without "test" when running affected:test
3 days ago by Victor Savkin
Succeeded
501
9750c6d8 feature(schematics): libraries should not be able to deep import themselves
3 days ago by Victor Savkin
Succeeded
584
732aa364 cleanup(schematics): removes an old path mapping
4 days ago by Victor Savkin
Succeeded
583
2f110a90 feat(schematics): add an option to run affected:* by only specifying --base
4 days ago by Victor Savkin
Succeeded
482
41bb0109 fix(schematics): default to workspace npm scope as the default prefix when creating apps and libs
4 days ago by Victor Savkin
Failed
34805
Flaky task→
e938661b fix(nx-cloud): download light client to tmp dir when outside nx workspace When not in an Nx workspace, the light client was downloaded to .nx/cache/cloud relative to cwd, creating unwanted .nx folders. Now uses os.tmpdir()/nx-cloud-client/<hash> keyed by NX_CLOUD_API URL.
4 days ago by Victor Savkin
Succeeded
477
459f62d1 fix(schematics): fix tests
6 days ago by Victor Savkin
Succeeded
master
035e061e fix(core): allow nx cloud commands to run outside of a workspace (#34728) ## Current Behavior Running Nx Cloud commands (login, logout, polygraph, etc.) from outside an Nx workspace fails with 'The current directory is not part of an Nx workspace' because handleNoWorkspace exits before reaching the cloud command handler. Additionally, polygraph was not in the isNxCloudCommand list. ## Expected Behavior Nx Cloud commands work regardless of whether you are inside an Nx workspace, since they only delegate to the cloud client. ## Related Issue(s) N/A --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
10 days ago by Victor Savkin
Succeeded
469
e0bd923c feat(schematics): change upgrade-module and downgrade-module schematics to work with CLI6
10 days ago by Victor Savkin
Succeeded
master
035e061e fix(core): allow nx cloud commands to run outside of a workspace (#34728) ## Current Behavior Running Nx Cloud commands (login, logout, polygraph, etc.) from outside an Nx workspace fails with 'The current directory is not part of an Nx workspace' because handleNoWorkspace exits before reaching the cloud command handler. Additionally, polygraph was not in the isNxCloudCommand list. ## Expected Behavior Nx Cloud commands work regardless of whether you are inside an Nx workspace, since they only delegate to the cloud client. ## Related Issue(s) N/A --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
10 days ago by Victor Savkin
Succeeded
master
d267145a fix(nx-cloud): allow download-cloud-client to work outside nx workspaces (#34746) Remove the isNxCloudUsed guard that prevented the command from running without an nx.json. Now gracefully falls back to default cloud URL when not in an Nx workspace.      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
10 days ago by Victor Savkin
Succeeded
master
d267145a fix(nx-cloud): allow download-cloud-client to work outside nx workspaces (#34746) Remove the isNxCloudUsed guard that prevented the command from running without an nx.json. Now gracefully falls back to default cloud URL when not in an Nx workspace.      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
10 days ago by Victor Savkin