Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Succeeded
master
11m 35s
f5d3ba5d docs(core): add some docs for maxCacheSize (#30569) ## Current Behavior `maxCacheSize` is not documented ## Expected Behavior `maxCacheSize` is documented ## Related Issue(s)  Fixes #
2 hours ago by AgentEnder
Succeeded
master
5m 49s
b50727ad docs(core): brew install nx (#30571) Adds instructions to install Nx globally with Homebrew
2 hours ago by isaacplmann
Succeeded
master
5m 25s
85bb61f9 fix(core): ensure rust code is able to handle null terminal outputs (#30494) ## Current Behavior Somewhere in the ts side we are passing a value as null for terminal outputs. The rust code bails when this happens. ## Expected Behavior The rust side is able to handle it. ## Related Issue(s)  Fixes #
3 hours ago by AgentEnder
Failed
master
1h 45m 47s
85bb61f9 fix(core): ensure rust code is able to handle null terminal outputs (#30494) ## Current Behavior Somewhere in the ts side we are passing a value as null for terminal outputs. The rust code bails when this happens. ## Expected Behavior The rust side is able to handle it. ## Related Issue(s)  Fixes #
3 hours ago by AgentEnder
Succeeded
master
45m 52s
093b13fe feat(core): handle yarn resolutions and patches when parsing and pruning lock file (#30546) This PR introduces support for `resolutions` and `patches` for yarn lock file parsing and pruning. Additionally, it fixes the correct dependency matching when the version has one of the two forms: - fluid version range (e.g. `npm:*`) - union version range (e.g. `1 || 2 || 3`) ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
5 hours ago by meeroslav
Failed
master
15m 50s
093b13fe feat(core): handle yarn resolutions and patches when parsing and pruning lock file (#30546) This PR introduces support for `resolutions` and `patches` for yarn lock file parsing and pruning. Additionally, it fixes the correct dependency matching when the version has one of the two forms: - fluid version range (e.g. `npm:*`) - union version range (e.g. `1 || 2 || 3`) ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
6 hours ago by meeroslav
Succeeded
master
6m 39s
028b5768 docs(core): correct kevin's twitter account (#30563) Fix Kevin Oliveira's twitter account
9 hours ago by isaacplmann
Succeeded
master
5m 57s
028b5768 docs(core): correct kevin's twitter account (#30563) Fix Kevin Oliveira's twitter account
9 hours ago by isaacplmann
Succeeded
master
5m 17s
028b5768 docs(core): correct kevin's twitter account (#30563) Fix Kevin Oliveira's twitter account
10 hours ago by isaacplmann
Succeeded
master
5m 27s
3afa91a5 fix(angular): use latest version of @analogjs/vitest-angular #30423 (#30560) ## Current Behavior The version of `@analogjs/vitest-angular` and `@analogjs/vite-plugin-angular` that is installed is `1.10.0` The latest version is `1.14.1`. ## Expected Behavior Upgrade to the latest version of the packages. ## Related Issue(s) Fixes #30423
12 hours ago by Coly010
Failed
master
3h 28m 12s
b8e43255 fix(nextjs): bumped to eslintConfigNextVersion to v15 (#30537) Closes #30536      ## Current Behavior The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next. ## Expected Behavior `npm install` should succeed without dependency conflicts. ## Related Issue(s) Fixes #30536 --------- Co-authored-by: Nicholas Cunningham <ndcunningham@gmail.com>
17 hours ago by FrozenPandaz
Succeeded
master
16m 6s
b8e43255 fix(nextjs): bumped to eslintConfigNextVersion to v15 (#30537) Closes #30536      ## Current Behavior The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next. ## Expected Behavior `npm install` should succeed without dependency conflicts. ## Related Issue(s) Fixes #30536 --------- Co-authored-by: Nicholas Cunningham <ndcunningham@gmail.com>
19 hours ago by JamesHenry
Succeeded
master
5m 39s
b8e43255 fix(nextjs): bumped to eslintConfigNextVersion to v15 (#30537) Closes #30536      ## Current Behavior The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next. ## Expected Behavior `npm install` should succeed without dependency conflicts. ## Related Issue(s) Fixes #30536 --------- Co-authored-by: Nicholas Cunningham <ndcunningham@gmail.com>
20 hours ago by DB-db-dron
Succeeded
master
30m 6s
b8e43255 fix(nextjs): bumped to eslintConfigNextVersion to v15 (#30537) Closes #30536      ## Current Behavior The current version of eslint-config-next (v14.2.16) has peer dependency conflicts with the latest versions of ESLint (v9.x). This issue causes npm install to fail in projects using eslint-config-next. ## Expected Behavior `npm install` should succeed without dependency conflicts. ## Related Issue(s) Fixes #30536 --------- Co-authored-by: Nicholas Cunningham <ndcunningham@gmail.com>
23 hours ago by DB-db-dron
Succeeded
master
5m 17s
6ba90cdb docs(misc): minor self-hosted cache docs fixes (#30554) Minor updates to wording for the self-hosted cache pages
1 day ago by juristr
Succeeded
master
5m 27s
6ba90cdb docs(misc): minor self-hosted cache docs fixes (#30554) Minor updates to wording for the self-hosted cache pages
1 day ago by juristr
Succeeded
master
5m 22s
29a2b18f fix(nx-dev): fix blog post links (#30553) Currently, links are broken to the latest Remote Caching blog post on these two pages: - https://nx.dev/blog/evolving-nx - https://nx.dev/blog/introducing-nx-powerpack <img width="885" alt="Screenshot 2025-03-31 at 2 39 38 PM" src="https://github.com/user-attachments/assets/2c6b3667-496a-4c40-b3de-8c7e911e4608" /> This PR fixes those and updates the timestamp to the correct date.
1 day ago by jaysoo
Succeeded
master
5m 14s
a22f4fce docs(misc): new self-hosted cache updates (#30550) Adds the new updates around self-hosted caching possibilities.
1 day ago by juristr
Succeeded
master
5m 51s
5974851c fix(js): infer dependency between `typecheck` and `build` tasks and more granular outputs for `typecheck` (#30549) ## Current Behavior There is no dependency between the inferred `typecheck` and `build` tasks. Depending on their run order, this can result in duplicated processing (type-checking, `.d.ts` generation). Given there's no explicit dependency, the order would be non-deterministic. Additionally, when `outDir` is set in the tsconfig files, it's used as-is in the currently inferred outputs for `typecheck`. This can result in extra files being cached for the task. ## Expected Behavior For optimum performance, the inferred `typecheck` task should depend on the `build` task. The `typecheck` task's outputs should be more granular so that only the relevant files (declaration files and declaration map files if enabled) are cached. ### Explanation Consider a typical setup with specific tsconfig file for files with different concerns: - tsconfig.lib.json: TS configuration for the library runtime files - tsconfig.spec.json: TS configuration for the unit test files - tsconfig.json: TS solution configuration, a solution file that references the specific config files above When running `tsc -b tsconfig.lib.json --verbose` (build), we can see how the `tsconfig.lib.json` TS project is built: ```bash Projects in this build: * tsconfig.lib.json Project 'tsconfig.lib.json' is out of date because output file 'dist/tsconfig.lib.tsbuildinfo' does not exist Building project '<workspace root>/packages/pkg1/tsconfig.lib.json'... ``` After that, if we run `tsc -b tsconfig.json --emitDeclarationOnly --verbose` (typecheck), we'll see how the `tsc` output for `tsconfig.lib.json` is reused: ```bash Projects in this build: * tsconfig.lib.json * tsconfig.spec.json * tsconfig.json Project 'tsconfig.lib.json' is up to date because newest input 'src/lib/file.ts' is older than output 'dist/tsconfig.lib.tsbuildinfo' Project 'tsconfig.spec.json' is out of date because output file 'out-tsc/jest/tsconfig.spec.tsbuildinfo' does not exist Building project '<workspace root>/packages/pkg1/tsconfig.spec.json'... ``` The relevant bit above is `Project 'tsconfig.lib.json' is up to date because newest input 'src/lib/file.ts' is older than output 'dist/tsconfig.lib.tsbuildinfo'`. Because the initial `build` task already typechecks and produces `.d.ts` files for the `tsconfig.lib.json`, when the `typecheck` task runs, `tsc` identifies that the outputs for that config files were already produced and can be reused. If we were to run the tasks in the inverse order, the results would be different: ```bash > npx tsc -b tsconfig.json --emitDeclarationOnly --verbose Projects in this build: * tsconfig.lib.json * tsconfig.spec.json * tsconfig.json Project 'tsconfig.lib.json' is out of date because output file 'dist/tsconfig.lib.tsbuildinfo' does not exist Building project '<workspace root>/packages/pkg1/tsconfig.lib.json'... Project 'tsconfig.spec.json' is out of date because output file 'out-tsc/jest/tsconfig.spec.tsbuildinfo' does not exist Building project '<workspace root>/packages/pkg1/tsconfig.spec.json'... > npx tsc -b tsconfig.lib.json --verbose Projects in this build: * tsconfig.lib.json Project 'tsconfig.lib.json' is out of date because buildinfo file 'dist/tsconfig.lib.tsbuildinfo' indicates there is change in compilerOptions Building project '<workspace root>/packages/pkg1/tsconfig.lib.json'... ``` Note how when the `build` task is run, `tsc` identifies that there was a change in `compilerOptions` (`--emitDeclarationOnly`) and it requires building the project. This is because the `typecheck` task only generates declaration files and the `build` task must also emit the transpiled `.js` files. ### Benchmark Running those two different flows in a simple (non-Nx) project with a TS configuration structure like the one mentioned above and with 5000 TS files split in half for runtime and test files yields the following: ```bash hyperfine -r 5 -p "rm -rf dist out-tsc" \ -n "build => typecheck" "npx tsc -b tsconfig.lib.json && npx tsc -b --emitDeclarationOnly" \ -n "typecheck => build" "npx tsc -b tsconfig.json --emitDeclarationOnly && npx tsc -b tsconfig.lib.json" Benchmark 1: build => typecheck Time (mean ± σ): 6.832 s ± 0.094 s [User: 11.361 s, System: 1.060 s] Range (min … max): 6.734 s … 6.985 s 5 runs Benchmark 2: typecheck => build Time (mean ± σ): 8.789 s ± 0.015 s [User: 14.817 s, System: 1.267 s] Range (min … max): 8.771 s … 8.812 s 5 runs Summary build => typecheck ran 1.29 ± 0.02 times faster than typecheck => build ``` ## Related Issue(s) Fixes #
1 day ago by leosvelperez
Succeeded
master
7m 10s
e29f8f0d chore(nx-dev): add todo comment for moving endpoint to nx api (#30286)
1 day ago by MaxKless