Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
21.5.x
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
9 days ago by jaysoo
Canceled
21.5.x
2976add1 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
9 days ago by jaysoo
Succeeded
21.5.x
7fb4e908 docs(misc): fix JSON parsing for project details with escaped quotes (#32778) Fixed the `parseAstroHtmlWrappedJson` function used by PDV and graph tag components to render code fence properly. The problem was that inner HTML with code fence caused escaped double-quotes (`\"`) to be improperly handled. By the time we read the HTML via React props, the escape character is already done (`\`). Thus, use code fence to let Starlight render the full block, and then parse out the JSON object from the `[data-code]` attribute on the div. For example, previously this would fail: ``` {% project_details %} { "foo": "\"bar\"" } {% /project_details %} ``` That doesn't work because the HTML is just ""bar"", which is invalid. But changing the above to this works: ```` {% project_details %} ```json { "foo": "\"bar\"" } ``` {% /project_details %} ```` This works because you get something like `data-code=""foo": "\"bar\"""` set on the `div`. So we can use regexp to match everything within that attribute and parse it out as JSON once we convert some entities. Check the [`nx-dev/ui-markdoc/src/lib/utils/parse-astro-html-wrapped-json.ts`](https://github.com/nrwl/nx/pull/32778/files#diff-c3d8e90b624e30217beaa44c46a16b9053533cf9a8542a4f7301ccaf3dbdab58) file for the full logic. Also added JSON code fences to all graph tags in mdoc files to ensure proper parsing. <img width="709" height="866" alt="Screenshot 2025-09-18 at 3 41 26 PM" src="https://github.com/user-attachments/assets/fdae86a6-929a-4a1f-82fe-7d4052de5db5" /> Closes #DOC-217 (cherry picked from commit fa5a1bf781b6da8caae30e49b6f56ed07877f67a)
9 days ago by jaysoo
Succeeded
21.5.x
486b7c40 fix(angular-rspack): ensure assets extracted from stylesheets correctly #32487 (#32759) ## Current Behavior When Angular components reference assets in their stylesheets using `url()` (e.g., `background-image: url('../assets/test-pattern.svg')`), the Nx Angular Rspack plugin processes the CSS but fails to extract and copy the referenced asset files to the output directory. This results in: - CSS is processed and URLs may be rewritten to reference output paths (e.g., `url('./media/test-pattern.svg')`) - The actual asset files are never copied to the output directory - Browser shows 404 errors for missing asset files when the application runs - No `media` directory is created in the build output ## Expected Behavior With this fix, assets referenced in component stylesheets are now properly extracted and emitted to the output directory: - Asset files referenced in component stylesheets are extracted and copied to the output directory - CSS URLs are correctly rewritten to point to the copied assets - No 404 errors occur for asset files - A `media` directory is created in the output with the extracted assets - Both inline and external component styles properly handle asset extraction ## Related Issue(s) Fixes #32487 ## Changes Made ### Core Fix - Modified the Angular Rspack plugin to properly collect and emit stylesheet assets during the compilation process - Added asset collection during both bundle file and inline style processing in `setup-compilation.ts` and `setup-with-angular-compilation.ts` - Implemented asset emission in the `processAssets` hook of the Angular Rspack plugin ### Test Coverage - Added comprehensive example application (`examples/angular-rspack/csr-css-assets`) that demonstrates: - External component stylesheets with asset references - Inline component styles with asset references - Various asset types (SVG, images) - Proper asset extraction and URL rewriting ### Technical Details The fix addresses the gap between Angular's `ComponentStylesheetBundler` which correctly processes assets and generates `outputFiles`, and the Nx Angular Rspack plugin which now properly emits these files using `compilation.emitAsset()` during the build process. (cherry picked from commit 36741d08d2fb7a28f037b05d01763a61e0b19400)
10 days ago by Coly010
Failed
21.5.x
486b7c40 fix(angular-rspack): ensure assets extracted from stylesheets correctly #32487 (#32759) ## Current Behavior When Angular components reference assets in their stylesheets using `url()` (e.g., `background-image: url('../assets/test-pattern.svg')`), the Nx Angular Rspack plugin processes the CSS but fails to extract and copy the referenced asset files to the output directory. This results in: - CSS is processed and URLs may be rewritten to reference output paths (e.g., `url('./media/test-pattern.svg')`) - The actual asset files are never copied to the output directory - Browser shows 404 errors for missing asset files when the application runs - No `media` directory is created in the build output ## Expected Behavior With this fix, assets referenced in component stylesheets are now properly extracted and emitted to the output directory: - Asset files referenced in component stylesheets are extracted and copied to the output directory - CSS URLs are correctly rewritten to point to the copied assets - No 404 errors occur for asset files - A `media` directory is created in the output with the extracted assets - Both inline and external component styles properly handle asset extraction ## Related Issue(s) Fixes #32487 ## Changes Made ### Core Fix - Modified the Angular Rspack plugin to properly collect and emit stylesheet assets during the compilation process - Added asset collection during both bundle file and inline style processing in `setup-compilation.ts` and `setup-with-angular-compilation.ts` - Implemented asset emission in the `processAssets` hook of the Angular Rspack plugin ### Test Coverage - Added comprehensive example application (`examples/angular-rspack/csr-css-assets`) that demonstrates: - External component stylesheets with asset references - Inline component styles with asset references - Various asset types (SVG, images) - Proper asset extraction and URL rewriting ### Technical Details The fix addresses the gap between Angular's `ComponentStylesheetBundler` which correctly processes assets and generates `outputFiles`, and the Nx Angular Rspack plugin which now properly emits these files using `compilation.emitAsset()` during the build process. (cherry picked from commit 36741d08d2fb7a28f037b05d01763a61e0b19400)
10 days ago by Coly010
Succeeded
21.5.x
45268fff feat(rspack): respect deleteOutputPath option in rspack executor (#32609) - Add deleteOutputPath option to rspack executor schema - Modify rspack executor to only clean output directory when deleteOutputPath is not explicitly set to false - This aligns rspack executor behavior with webpack executor and allows users to control output cleaning - Fixes issue where rspack.output.clean configuration was being bypassed Fixes #32015      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: Colum Ferry <cferry09@gmail.com>
17 days ago by omer-za
Failed
21.5.x
5a88b520 chore(core): remove unused import (#32691)      ## Current Behavior  Import is unused ## Expected Behavior  Import is removed ## Related Issue(s)  Fixes #
18 days ago by FrozenPandaz
Failed
21.5.x
419e2c1f fix(core): filter task duration estimation by successful tasks only (#32688) ## Current Behavior Task duration estimation includes all task runs regardless of their status (success, failure, cancelled), which can lead to inaccurate timing predictions. ## Expected Behavior Task duration estimation should only consider successful task runs to provide more accurate timing estimates for future task execution planning. ## Related Issue(s) Fixes inaccurate task duration estimation by filtering out failed/cancelled tasks from the calculation. ## Changes Made - Modified SQL query in `get_estimated_task_timings` to filter by `status = 'success'` - Added database index on `status` column to improve query performance - Updated both the WHERE clause condition and table schema initialization (cherry picked from commit bc359216908ebbddccfdad1d013bd120b1075b2b)
18 days ago by FrozenPandaz
Canceled
21.5.x
6575b808 chore(core): remove unused import (#32689)      ## Current Behavior  The import is unused ## Expected Behavior  The import is removed ## Related Issue(s)  Fixes # (cherry picked from commit 3d6e304580abcd4a1056ecda7b727da38e58cf16)
18 days ago by FrozenPandaz
Succeeded
21.5.x
05df41a9 chore(repo): add CI check to prevent tracked files being listed in .gitignore (#32460) > [!NOTE] > CI is failing on this PR right now, its expected. We don't currently adhere to this advice, and its causing issues. This PR should represent a sync of this, and future protection ## Current Behavior Previously, we had no automated check to detect when files tracked by Git were inadvertently listed in `.gitignore`. This could lead to inconsistent behavior in Nx's caching system. ## Expected Behavior With this PR, the CI pipeline now includes a check (`check-git-ignored-tracked-files`) that identifies tracked files that would be ignored by Git if they weren't already being tracked. This ensures consistency in Nx's cache hash calculation. ## Why This Matters for Nx This check is critical for Nx's caching system because: **Hash Calculation Consistency**: Nx calculates cache hashes based on the files that Git tracks. When a file is both tracked by Git and listed in `.gitignore`, it creates an inconsistency where: - Git includes the file in operations (and Nx hash calculations) - `.gitignore` indicates the file should be ignored - This can lead to different hash calculations depending on timing and environment **Impact on Cache Performance**: - **Cache Misses**: Valid cache entries may be missed due to hash discrepancies - **Unreliable Builds**: Tasks may not re-run when they should, or may re-run unnecessarily - **Cross-Environment Issues**: Different developers or CI environments may calculate different hashes for identical code **The Solution**: The new script identifies these problematic files and provides clear remediation steps: - For files that shouldn't be tracked: `git rm --cached <file>` - For files that should be tracked: Update `.gitignore` to be more specific This ensures that Nx's intelligent caching system works as designed, providing fast, reliable builds across the entire development workflow. ## Related Issue(s) Fixes the inconsistency between Git tracking and ignore patterns that can affect Nx cache hash calculations. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> (cherry picked from commit 44b0c61a29a3492383388fc0559583c9d143da85)
18 days ago by AgentEnder