Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
master
0e779e50 fix(core): use require for global to local Nx handoff so Windows drive paths work (#35478)
by Leosvel Pé...
Succeeded
33655
cdc3e729 fix(core): clean up per-task process listeners on child exit Each RunningNodeProcess registered process-level listeners (exit, and SIGINT/SIGTERM/SIGHUP in the forked path) without ever removing them, causing MaxListenersExceededWarning on workspaces with many parallel run-commands tasks. Store the handlers as named refs and remove them when the child exits or errors. Mirrors the pattern from #35279, adapted to the current architecture (killPromise guard + NX_FORKED_TASK_EXECUTOR gate).
by Leosvel Pé...
Succeeded
master
0e779e50 fix(core): use require for global to local Nx handoff so Windows drive paths work (#35478)
by Leosvel Pé...
Succeeded
master
0e779e50 fix(core): clean up per-task process listeners on child exit Each RunningNodeProcess registered process-level listeners (exit, and SIGINT/SIGTERM/SIGHUP in the forked path) without ever removing them, causing MaxListenersExceededWarning on workspaces with many parallel run-commands tasks. Store the handlers as named refs and remove them when the child exits or errors. Mirrors the pattern from #35279, adapted to the current architecture (killPromise guard + NX_FORKED_TASK_EXECUTOR gate).
by Leosvel Pé...
Failed
33655
Flaky task→
cdc3e729 fix(core): clean up per-task process listeners on child exit Each RunningNodeProcess registered process-level listeners (exit, and SIGINT/SIGTERM/SIGHUP in the forked path) without ever removing them, causing MaxListenersExceededWarning on workspaces with many parallel run-commands tasks. Store the handlers as named refs and remove them when the child exits or errors. Mirrors the pattern from #35279, adapted to the current architecture (killPromise guard + NX_FORKED_TASK_EXECUTOR gate).
by Leosvel Pé...
Canceled
35477
bdcfb70b chore(graph): bust graph-client build-client cache to validate sandbox fix
by Leosvel Pé...
Succeeded
master
0e779e50 fix(core): use require for global to local Nx handoff so Windows drive paths work (#35478)
by Leosvel Pé...
Succeeded
35472
ced0b5ab chore(nx-dev): resolve astro-docs:build sandbox violations - Declare plugin schemas/docs and dependent task outputs as inputs so cache invalidation tracks the files astro-docs actually consumes. - Stop TypeDoc from writing tsconfig.lib.json into devkit's dist output; use a tempDir copy with absolute include paths anchored at the dist directory. - Load create-nx-workspace from compiled dist instead of ts-node-ing source, eliminating cnw source reads from the build sandbox. - Tighten astro-docs/tsconfig.json exclude to keep e2e and eslint config out of the main TS project. - Exclude tests, eslint configs, tsconfig*.json, and e2e/ from Tailwind oxide source scanning so it stops parsing files that cannot contain class usages. - Move rollup-examples.md to packages/rollup/docs/ to match every other plugin and remove the need for an src/docs glob in inputs. - Declare the workspace tsconfig as a selective JSON input so esbuild's ancestor walk-up registers as declared without making the cache sensitive to references-only changes.
by Leosvel Pé...
Succeeded
35478
6d9c46bf fix(core): use require for global to local Nx handoff so Windows drive paths work
by Leosvel Pé...
Succeeded
35477
b4202b9b fix(bundling): include tsconfig solution input for webpack
by Leosvel Pé...
Succeeded
35472
24b5ad1f chore(nx-dev): resolve astro-docs:build sandbox violations - Declare plugin schemas/docs and dependent task outputs as inputs so cache invalidation tracks the files astro-docs actually consumes. - Stop TypeDoc from writing tsconfig.lib.json into devkit's dist output; use a tempDir copy with absolute include paths anchored at the dist directory. - Load create-nx-workspace from compiled dist instead of ts-node-ing source, eliminating cnw source reads from the build sandbox. - Tighten astro-docs/tsconfig.json exclude to keep e2e and eslint config out of the main TS project. - Exclude tests, eslint configs, tsconfig*.json, and e2e/ from Tailwind oxide source scanning so it stops parsing files that cannot contain class usages. - Move rollup-examples.md to packages/rollup/docs/ to match every other plugin and remove the need for an src/docs glob in inputs. - Declare the workspace tsconfig as a selective JSON input so esbuild's ancestor walk-up registers as declared without making the cache sensitive to references-only changes.
by Leosvel Pé...
Succeeded
35471
58b1d709 chore(repo): resolve sandbox violations on graph-client:build-client task
by Leosvel Pé...
Canceled
35471
b3dddb16 chore(repo): cache-bust graph-client:build-client to verify sandboxing exclusions
by Leosvel Pé...
Succeeded
35476
139c4fcf fix(bundling): include tsconfig solution input for rollup Add the field-scoped root tsconfig input to rollup target defaults and inferred build targets so cache keys include ts solution setup changes.
by Leosvel Pé...
Canceled
35471
42c6508c chore(repo): resolve sandbox violations on graph-client:build-client task Webpack snapshots context dirs registered by postcss-loader via tailwind's `dir-dependency` emission, so it hashes `*.stories.*` and `*.spec.*` files in graph-client and its deps. Add a task-level exclude-reads entry covering those files — they're excluded from inputs and never enter the bundle. Also fix this repo's tailwind content globs to actually exclude stories and specs (drop the leading `*` before `!()` where present, add the negation where missing).
by Leosvel Pé...
Succeeded
master
278568aa fix(misc): resolve pnpm catalog: refs in version lookups (#35459) ## Current Behavior `@nx/react:application` (and any path that calls `@nx/vite` or `@nx/vitest` `ensureDependencies`) crashes when the root `package.json` declares `vite` via a pnpm catalog alias such as `"vite": "catalog:"` or `"vite": "catalog:tooling"`: ``` NX Invalid version. Must be a string. Got type "object". TypeError ... at new SemVer ... at major ... at ensureDependencies ``` `@nx/storybook`'s `convert-to-inferred` migration is broken in the same way: `getInstalledPackageVersion` reads dependencies straight from `package.json` with no catalog resolution, so a literal `catalog:` value reaches `coerce` and throws via `major(null)` in `getInstalledPackageVersionInfo`. ## Expected Behavior - pnpm catalog aliases in `package.json` are resolved through `pnpm-workspace.yaml` (default and named catalogs) before semver parsing. - When the resolved/raw range is not coercible (missing catalog entry, missing `pnpm-workspace.yaml`, `workspace:*`, `link:`, `file:`, `git:`), the code falls back to the existing default rather than throwing. - Existing v4-vs-v6 `@vitejs/plugin-react` selection for plain semver ranges is preserved. ## Changes - `@nx/vite` / `@nx/vitest`: `ensureDependencies` now reads `vite` via `getDependencyVersionFromPackageJson` (catalog-aware) and null-guards the `coerce` result. - `@nx/storybook`: `getInstalledPackageVersion` now uses `getDependencyVersionFromPackageJson`, and `getInstalledPackageVersionInfo` null-guards `coerce`. - Tests added in `packages/vite/src/utils/ensure-dependencies.spec.ts` for named catalog, default catalog, missing catalog entry, and unparseable ranges (`workspace:*`). ## Related Issue(s) Fixes #35453
by Leosvel Pé...
Succeeded
master
1d6f14df fix(node): include tsconfig input in node-app esbuild scaffold (#35466) ## Current Behavior The node app generator with `bundler=esbuild` does not include the field-scoped `tsconfig.json` input needed for proper cache hashing. This means builds may return stale cached results when the workspace's `tsconfig.json` is edited (e.g., changing `extends`, `files`, or `include` fields). ## Expected Behavior The node app generator now includes `TS_SOLUTION_SETUP_TSCONFIG_INPUT` as an input for `@nx/esbuild:esbuild` targets, ensuring cache hashes properly reflect changes to the workspace root `tsconfig.json`. Additionally, exports `TS_SOLUTION_SETUP_TSCONFIG_INPUT` from `@nx/js` so other Nx packages can reuse this constant for their own executors and plugins.
by Leosvel Pé...
Canceled
master
7581dfe3 fix(misc): exclude stories and specs from tailwind content scanning (#35470) ## Current Behavior The default tailwind content glob in `@nx/react/tailwind` and `@nx/vue/tailwind` helpers, plus their `setup-tailwind` generator templates, is meant to skip `*.stories.*` and `*.spec.*` files, but the leading `*` in the `!()` extglob makes the negation a no-op — story and spec classes end up scanned alongside production code. ## Expected Behavior Stories and specs are excluded from tailwind content scanning, matching the intent of the existing pattern. ## Technical details The current pattern `*!(*.stories|*.spec).{...}` fails because the leading `*` lets the matcher split the input across `*` and `!()` (e.g., `foo.stories` → `*` = `foo.`, `!()` = `stories`, which doesn't end in `.stories`), so the file matches the glob and gets included. Removing the leading `*` makes `!(*.stories|*.spec)` apply to the full filename portion. Affects: - `packages/react/tailwind.ts` (helper default) - `packages/vue/tailwind.ts` (helper default) - `packages/react/src/generators/setup-tailwind/files/tailwind.config.js__tmpl__` - `packages/vue/src/generators/setup-tailwind/files/tailwind.config.js.template`
by Leosvel Pé...
Failed
master
1d892d73 fix(js): include extended tsconfigs from project references in typecheck inputs (#35457) ## Current Behavior The `@nx/js/typescript` plugin walks the project reference chain to collect tsconfig paths as inputs for the inferred `typecheck` target, but does not follow `extends` chains on those referenced tsconfigs. When `tsc --build` walks into an external project reference whose `tsconfig.lib.json` extends a sibling tsconfig (e.g. `./tsconfig.json`), that extended file is read at compile time but is not declared as an input — causing sandbox violations and incorrect cache keys for the consumer's `typecheck` task. ## Expected Behavior The plugin walks `extends` chains for every tsconfig visited during the reference chain traversal, emitting `^{projectRoot}/...` patterns for the extended files alongside the existing reference-chain patterns. Tasks consuming external project references with `extends` chains now correctly declare the full set of tsconfig files tsc reads. ## Changes `getExternalProjectReferenceTsconfigPatterns` now walks `extends` for each tsconfig visited during the worklist traversal. The walk: - Reuses the same `visited` set as the reference-chain walk (no redundant work). - Reuses the cached parsed tsconfig data (`tsConfigCacheData`) and `getConfigContext` cache (no extra parsing). - Pushes extended files onto the same worklist so extends-of-extends and references-from-extends are covered transitively. - Skips workspace-root files (no owning project) — those are already covered by the local project's existing extends walk. Patterns emit in the same `^{projectRoot}/relPath` form as the rest of the function, so the existing transitive resolution through the project graph applies unchanged. A focused unit test pins the new behavior: a project with an external ref whose `tsconfig.lib.json` extends a same-project `tsconfig.shared.json` correctly emits `^{projectRoot}/tsconfig.shared.json` as an input.
by Leosvel Pé...
Succeeded
35472
34b521a5 chore(nx-dev): resolve astro-docs:build sandbox violations - Declare plugin schemas/docs and dependent task outputs as inputs so cache invalidation tracks the files astro-docs actually consumes. - Stop TypeDoc from writing tsconfig.lib.json into devkit's dist output; use a tempDir copy with absolute include paths anchored at the dist directory. - Load create-nx-workspace from compiled dist instead of ts-node-ing source, eliminating cnw source reads from the build sandbox. - Tighten astro-docs/tsconfig.json exclude to keep e2e and eslint config out of the main TS project.
by Leosvel Pé...