Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
e3eedf9e docs(misc): update the docs to use more direct language (#34264)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
3 hours ago by pull[bot]
Succeeded
master
25112153 fix(nx-dev): make headers and table options linkable (#34267) - fix(nx-dev): always link headers regardless of mdoc or markdown content source (generated vs static file) - fix(nx-dev): make option/property columns in table linkable - the table column header is matched on `options`, `option`, `properties`, and property` (case insensitive) https://github.com/user-attachments/assets/7250b9d5-1030-4ebc-9e21-0a05f295bbf5 Note bc mdoc and `renderMarkdown` go through 2 different rendering pipelines, this logic must bc within the markdoc config and rehype (markdown) processing logic. tried to shared logic where I could --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
11 hours ago by pull[bot]
Succeeded
master
9790910f fix(angular): only throw "define" error when options.define has keys (#33969) ## Current Behavior The dev-server builder throws an error about the "define" option not being supported in Angular < 21, even when users don't configure it. The validation uses a truthy check that treats empty objects `{}` as true. ## Expected Behavior The error should only throw when users explicitly configure define with actual keys. ## Related Issues Fixes #33964 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: leosvelperez <12051310+leosvelperez@users.noreply.github.com>
1 month ago by pull[bot]
Succeeded
master
dd7ec301 feat(core): support cwd specific hashes (#33879) ## Current Behavior There is no straight-forward way to use the cwd as part of a tasks hash ## Expected Behavior You can use `{workingDirectory: 'absolute'}` to factor the working directory into the hash ## Related Issue(s)  Fixes #33684
1 month ago by pull[bot]
Succeeded
master
9790910f fix(angular): only throw "define" error when options.define has keys (#33969) ## Current Behavior The dev-server builder throws an error about the "define" option not being supported in Angular < 21, even when users don't configure it. The validation uses a truthy check that treats empty objects `{}` as true. ## Expected Behavior The error should only throw when users explicitly configure define with actual keys. ## Related Issues Fixes #33964 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: leosvelperez <12051310+leosvelperez@users.noreply.github.com>
1 month ago by pull[bot]
Succeeded
master
dd7ec301 feat(core): support cwd specific hashes (#33879) ## Current Behavior There is no straight-forward way to use the cwd as part of a tasks hash ## Expected Behavior You can use `{workingDirectory: 'absolute'}` to factor the working directory into the hash ## Related Issue(s)  Fixes #33684
1 month ago by pull[bot]
Succeeded
master
9475bb43 fix(core): ensure no tui on single tasks (#33910) ## Current Behavior The tui shouldn't show for single tasks ## Expected Behavior The tui isn't shown for single tasks ## Related Issue(s)  Fixes #
1 month ago by pull[bot]
Succeeded
master
9475bb43 fix(core): ensure no tui on single tasks (#33910) ## Current Behavior The tui shouldn't show for single tasks ## Expected Behavior The tui isn't shown for single tasks ## Related Issue(s)  Fixes #
1 month ago by pull[bot]
Failed
master
6e426514 chore(repo): update nx to 22.3.0-beta.3 (#33907) Updating Nx from 22.3.0-beta.2 to 22.3.0-beta.3
1 month ago by pull[bot]
Succeeded
master
6323dba8 fix(core): convert * to workspace:* for pnpm/yarn/bun in CNW (#33893) Templates use `"*"` for workspace dependencies in individual package.json files. This works for npm but breaks pnpm, yarn, and bun which require the `workspace:` protocol for proper symlinking. For pnpm, yarn, and bun: automatically convert `"*"` dependencies to `"workspace:*"` in all workspace package.json files. npm is left unchanged since it handles `"*"` natively. Also adds support for 2-level nested projects (e.g., `libs/shared/models/package.json`). Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
1 month ago by pull[bot]
Succeeded
master
ad7dfe78 fix(core): improve performance of buildExplicitPackageJsonDependencies (#33791) Further improvement of the graph creation. Improving the `buildExplicitPackageJsonDependencies`. | | Before | After | | ---- | ----- | ---- | | buildExplicitPackageJsonDependencies | 128 | 12 | | isPackageJsonAtProjectRoot | 114 | 1 | Fixes # --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
2 months ago by pull[bot]
Succeeded
master
15a7d954 fix(angular): improve error message when using esbuild-based build targets and generating cypress ct (#33846) ## Current Behavior When running `nx g @nx/angular:cypress-component-configuration` on an Angular project that uses esbuild (the default bundler since Angular 17), users receive a confusing error message: ```bash Unable to find a valid build configuration. Try passing in a target for an Angular app. ``` This doesn't explain why the configuration fails or what the actual limitation is. ## Expected Behavior Users now receive a clear, informative error message that explains: - Cypress Component Testing for Angular requires a webpack-based build target - Their project uses an esbuild-based executor (and which one) - Cypress only supports webpack as the bundler for Angular component testing This helps users understand the limitation and make informed decisions about how to proceed. ## Related Issue(s) Fixes #33329
2 months ago by pull[bot]
Succeeded
master
ed09ee1d fix(core): create all tables upfront when creating the database (#33843) Create all the tables upfront when creating the database. This prevents some issues in some scenarios where a missing table is reported.
2 months ago by pull[bot]
Succeeded
master
ed09ee1d fix(core): create all tables upfront when creating the database (#33843) Create all the tables upfront when creating the database. This prevents some issues in some scenarios where a missing table is reported.
2 months ago by pull[bot]
Succeeded
master
15a7d954 fix(angular): improve error message when using esbuild-based build targets and generating cypress ct (#33846) ## Current Behavior When running `nx g @nx/angular:cypress-component-configuration` on an Angular project that uses esbuild (the default bundler since Angular 17), users receive a confusing error message: ```bash Unable to find a valid build configuration. Try passing in a target for an Angular app. ``` This doesn't explain why the configuration fails or what the actual limitation is. ## Expected Behavior Users now receive a clear, informative error message that explains: - Cypress Component Testing for Angular requires a webpack-based build target - Their project uses an esbuild-based executor (and which one) - Cypress only supports webpack as the bundler for Angular component testing This helps users understand the limitation and make informed decisions about how to proceed. ## Related Issue(s) Fixes #33329
2 months ago by pull[bot]
Succeeded
master
60fffd3c feat(js): add option for using tsgo compiler when inferring build and typecheck tasks (#33821) Adds a 'compiler' option to the @nx/js/typescript plugin configuration, with options 'tsc' and 'tsgo'. Affects both typecheck and build targets. ## Current Behavior The `@nx/js/typescript` plugin always uses `tsc` as the compiler, with no way to use the native `tsgo` preview. ## Expected Behavior The `@nx/js/typescript` plugin can be configured to use `tsgo` for building and typechecking. ## Related Issue(s) Related discussion #32591.
2 months ago by pull[bot]
Succeeded
master
1310ee6f docs(misc): mcp client list cleanup (#33826) 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>
2 months ago by pull[bot]
Succeeded
master
205daee6 fix(webpack): interpolate process.env more verbosely to reduce bundle size with DefinePlugin (#30826) ## Current Behavior When we prepare ENVs for the DefinePlugin, we are creating the `process.env` object. For example: ``` // .env NX_PUBLIC_VALUE1=1 NX_PUBLIC_VALUE2=2 NX_PUBLIC_VALUE3=3 ``` As result we will have: ```js { 'process.env': { "NX_PUBLIC_VALUE1": "1", "NX_PUBLIC_VALUE2": "2", "NX_PUBLIC_VALUE3": "3" } } ``` As a result, in the final bundle, we will replace process.env with this object. The issue: If I use all 3 values in my application DefinePlugin will inject this object 3 times, instead of injecting it once. It will look like that: ```js const a = { "NX_PUBLIC_VALUE1": "1", "NX_PUBLIC_VALUE2": "2", "NX_PUBLIC_VALUE3": "3" }.NX_PUBLIC_VALUE1 const b = { "NX_PUBLIC_VALUE1": "1", "NX_PUBLIC_VALUE2": "2", "NX_PUBLIC_VALUE3": "3" }.NX_PUBLIC_VALUE2 const c = { "NX_PUBLIC_VALUE1": "1", "NX_PUBLIC_VALUE2": "2", "NX_PUBLIC_VALUE3": "3" }.NX_PUBLIC_VALUE3 ``` ## Expected Behavior DefinePlugin injects values instead of env object in each place ```js const a = "1" const b = "2" const c = "3" ``` ## Fixes - fixed this issue for webpack - fixed this issue for storybook - fixed this issue for rspack TLDR: now we have object like so: ```js { "process.env.NX_PUBLIC_VALUE1": "1", "process.env.NX_PUBLIC_VALUE2": "2", "process.env.NX_PUBLIC_VALUE3": "3" } ``` --------- Co-authored-by: Colum Ferry <cferry09@gmail.com>
2 months ago by pull[bot]
Succeeded
master
60d019e0 Revert "docs(nx-cloud): update resource usage minimum version to 22.2" (#33725) Reverts nrwl/nx#33723
2 months ago by pull[bot]
Succeeded
master
6c2c50d8 docs(nx-dev): update youtube link in resource usage article (#33724)
2 months ago by pull[bot]