Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
34823
636be203 chore(core): review feedback
6 minutes ago by Craigory C...
In progress
35138
eb4fa3aa fix(core): display actual error message when plugin loading fails When a plugin loaded in an isolated worker fails, the error is serialized as a plain object (not an Error instance). The existing `instanceof Error` check falls through to `new Error(String(reason))`, which produces `[object Object]` instead of the actual error message. Add a `reasonToError` helper that extracts the `message` and `stack` properties from serialized error objects before falling back to `String()` conversion. Fixes #35137
13 minutes ago by Steven Nance
In progress
master
d579fbfb fix(core): clean up legacy .gemini/skills during configure-ai-agents (#35117) ## Current Behavior When `configure-ai-agents` runs for Gemini, it copies skills to the shared `.agents/skills` directory (used by Codex, Cursor, and Gemini). However, workspaces that were configured with an older version of Nx still have a `.gemini/skills` directory containing duplicate Nx-managed skills. These legacy files are never cleaned up, leaving stale duplicates in the workspace. ## Expected Behavior When `configure-ai-agents` runs for Gemini, it should remove any `.gemini/skills` entries that also exist in `.agents/skills` (indicating they are Nx-managed skills that have been migrated). User-created custom skills in `.gemini/skills` that have no counterpart in `.agents/skills` are preserved. ## Related Issue(s) N/A — discovered during investigation of template repo AI agent configurations. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
21 minutes ago by MaxKless
In progress
34944
e27ab90c Merge branch 'master' into fix/34692-ai-agents-none
24 minutes ago by Jason Jean
In progress
35107
9d2d38a4 chore(core): adjust error when trying to resolve a migration and hitting a previous version [Self-Healing CI Rerun]
24 minutes ago by nx-cloud[bot]
In progress
35122
324c3dfc fix(repo): scope e2e eslint to test files only, cap warnings per project, remove conformance rule - e2e .eslintrc.json now only un-ignores test files (avoids exposing unrelated errors in non-test TS files) - Per-project max-warnings caps set for graph-client(15), nx-dev-feature-package-schema-viewer(7), nx-dev-ui-markdoc(7) - Removed the no-disabled-tests conformance rule since ESLint now covers the same ground - Ignored Maven target/ build output from linting
29 minutes ago by Jason Jean
In progress
35116
2e9d0a5f fix(vite): use TempFs with proper setup in plugin-with-test spec Add TempFs with package-lock.json, tsconfig.lib.json, and isUsingTsSolutionSetup mock to preserve original test behavior.
40 minutes ago by Jason Jean
Failed
35078
Fix ready→
9185f427 chore(repo): format benchmark files Co-authored-by: FrozenPandaz <FrozenPandaz@users.noreply.github.com>
43 minutes ago by nx-cloud[bot]
Canceled
35078
8537d154 chore(repo): format benchmark files Co-authored-by: FrozenPandaz <FrozenPandaz@users.noreply.github.com>
45 minutes ago by nx-cloud[bot]
Canceled
35116
72130e5d fix(vite): use TempFs with proper setup in plugin-with-test spec Add TempFs with package-lock.json, tsconfig.lib.json, and isUsingTsSolutionSetup mock to preserve original test behavior.
48 minutes ago by Jason Jean
In progress
master
0a0d43e6 fix(repo): correct build target outputs for docker and vue packages (#35136) ## Current Behavior - The `docker` package has its build output path pointing to `{workspaceRoot}/build/packages/docker/README.md`, but the `copy-readme.js` script writes to `dist/packages/docker/README.md`. This means the cache output doesn't match the actual output location. - The `vue` package has an empty build target (`{}`) with no README copy step, unlike every other publishable package. ## Expected Behavior - The `docker` package output path correctly points to `{workspaceRoot}/dist/packages/docker/README.md`. - The `vue` package has a proper build target that copies and processes the README, matching the pattern used by all other packages. ## Related Issue(s) N/A — found during audit of build target outputs.
48 minutes ago by Jason Jean
Canceled
35116
d1dc78b6 fix(core): add project name to TempFs package.json to restore build-deps/watch-deps targets
55 minutes ago by Jason Jean
Succeeded
1231
9ed26e6d
60 minutes ago by pull[bot]
Succeeded
master
37eb4ecd fix(bundling): bump esbuild for new projects to a version compatible with vite 8 (#35132) ## Current Behavior Newly generated JS/esbuild-based projects still default `esbuild` to `^0.19.2`. That conflicts with Vite 8 which requires `esbuild ^0.27.0`. ## Expected Behavior Newly generated projects should default to an `esbuild` version compatible with Vite 8. If a workspace already has `esbuild` installed, generators should preserve that version instead of blindly bumping it, and Vite init should fall back to Vite 7 with a warning when the installed `esbuild` range is incompatible with Vite 8. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
60 minutes ago by Leosvel Pé...
Succeeded
master
37eb4ecd fix(bundling): bump esbuild for new projects to a version compatible with vite 8 (#35132) ## Current Behavior Newly generated JS/esbuild-based projects still default `esbuild` to `^0.19.2`. That conflicts with Vite 8 which requires `esbuild ^0.27.0`. ## Expected Behavior Newly generated projects should default to an `esbuild` version compatible with Vite 8. If a workspace already has `esbuild` installed, generators should preserve that version instead of blindly bumping it, and Vite init should fall back to Vite 7 with a warning when the installed `esbuild` range is incompatible with Vite 8. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
1 hour ago by Leosvel Pé...
In progress
35108
94ff95d0 Merge branch 'master' into lourw/cont-tasks
1 hour ago by Louie Weng
Failed
35088
Flaky task→
d3906a63 fix(core): daemon !== ai agent [Self-Healing CI Rerun]
1 hour ago by nx-cloud[bot]
Failed
35126
26f366a6 fix(react): error when adding React Router app to workspace with Vite 8 ## Current Behavior When a user has an existing workspace with Vite 8 (the default for new Nx workspaces) and tries to add a React Router application, the generator silently produces a project with conflicting Vite types, causing typecheck failures. The react-router typecheck e2e test was also skipped due to this version conflict. ## Expected Behavior The generator throws a clear error when React Router is selected and Vite 8 is already installed, telling users to downgrade to Vite 7 first. This follows the same pattern used by Cypress component testing. The e2e test is re-enabled since the underlying typecheck works correctly for fresh workspaces (where Vite 7 is installed via the useViteV7 flag). ## Related Issue(s) Fixes NXC-4182
1 hour ago by Jack Hsu
Failed
35088
Flaky task→
7b1c57b8 fix(core): daemon !== ai agent [Self-Healing CI Rerun]
2 hours ago by nx-cloud[bot]
Succeeded
master
cbeedca9 chore(repo): add root tsconfig.json to nx-dev-e2e lint inputs (#35130) ## Current Behavior `nx-dev-e2e` has no `tsconfig.json`. When `eslint .` runs, `@typescript-eslint/parser` walks up from the project root to the workspace root `tsconfig.json`. This read is not declared as a lint input, causing a sandbox violation. ## Expected Behavior A minimal `tsconfig.json` extending `tsconfig.base.json` exists in the project, so the parser resolves locally and the sandbox violation is eliminated. ## Why not fix in the `@nx/eslint/plugin`? The plugin would need to resolve the ESLint config chain, identify which parser is in use, and replicate that parser's tsconfig resolution logic (walking up directories, following `extends` chains). This adds file I/O and config parsing to `createNodesV2`, which runs on the critical path during project graph computation — every `nx` command pays the cost. Not worth it for an edge case that only surfaces when a project has no local tsconfig. ## Why not an input override? An input override in `project.json` would duplicate the plugin's inferred inputs and could drift if the plugin changes what it infers in the future.
2 hours ago by Leosvel Pé...