Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Recorded
20.5.0
4f3118d5 chore(repo): update nx to 20.5.0-rc.4 (#30296)      ## Current Behavior  This repo uses Nx `20.5.0-rc.3` ## Expected Behavior  This repo uses Nx `20.5.0-rc.4` ## Related Issue(s)  Fixes #
6 days ago by FrozenPandaz
Recorded
20.5.0-rc.4
442058a2 Revert "feat(core): add activate key (#30250)" (#30295)
6 days ago by FrozenPandaz
Recorded
20.5.0-rc.3
5b034965 feat(core): add activate key (#30250)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
7 days ago by FrozenPandaz
Recorded
20.5.0-rc.2
00e970a0 docs(nx-dev): update team members (#30272) Updated titles for existing team members to reflect current roles. Added new team members, Nate Bohn and Steven Nance, along with their corresponding images.
7 days ago by FrozenPandaz
Succeeded
20.5.0-rc.1
bf10eae4 fix(angular): correct nx angular migration requirement for 19.2 (#30234)      ## Current Behavior Angular migrations require @angular/core@19.2.0, to update to 19.2.0 ## Expected Behavior Angular migrations require @angular/core@19.1.0 to update to 19.2.0 ## Related Issue(s)  Fixes # --------- Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
9 days ago by FrozenPandaz
Succeeded
20.5.0-rc.0
5382c8af fix(core): ensure daemon enabled check is unchanged (#30228)
12 days ago by FrozenPandaz
Succeeded
20.5.0-beta.5
4fe4fe95 fix(vite): allow force ignore of logs from nxViteTsPaths plugin #29320 (#30200) ## Current Behavior When Vite build is run where: - `nxViteTsPaths` plugin is enabled - `--verbose` or `NX_VERBOSE_LOGGING=true` is set The resulting logs can be quite noisy. ## Expected Behavior When `debug` is explicitly set to false, ignore logs even when `--verbose` is passed. Usage: ```ts nxViteTsPaths({ debug: false }) ``` ## Related Issue(s) Fixes #29320 --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com>
13 days ago by FrozenPandaz
Succeeded
20.5.0-beta.4
b9221bfe fix(core): fix typescript dependency calculation (#30131)
20 days ago by FrozenPandaz
Succeeded
20.5.0-beta.3
13319a85 fix(js): improve the `@nx/js/typescript` plugin performance (#30024) Improve the perf of the `@nx/js/typescript` plugin both in cold and warm scenarios. The main changes done are: - Batch some processing to do it once instead of doing it per config file (avoids some duplicated processing) - Use a custom TS host to read tsconfig files to reduce I/O operations - Cache tsconfig files' reads Benchmark results in a repo with 656 TS projects: ``` # Before the changes Cold (NX_CACHE_PROJECT_GRAPH=false): ~2285 ms Warm (NX_CACHE_PROJECT_GRAPH=true): ~2142 ms # After the changes Cold (NX_CACHE_PROJECT_GRAPH=false): ~597 ms Warm (NX_CACHE_PROJECT_GRAPH=true): ~220 ms ``` Note: Once https://github.com/nrwl/nx/pull/29935 is merged. I'll send another change to batch the file hashes. ## Current Behavior ## Expected Behavior ## Related Issue(s) Fixes #
27 days ago by jaysoo
Succeeded
20.5.0-beta.2
8bd0bcdd fix(js): generate pacakge.json for non-buildable nest and expo libs (#29891) This PR fixes a couple of issues for TS solution setup: 1. Expo library should generate with correct `package.json` file (e.g. `exports` maps either to source or dist). See [spec file](https://github.com/nrwl/nx/pull/29891/files#diff-ae2eb3d10d58786c17aa21f5603043b68043faaebafaec77912f3d69ac0c5295). 2. Nest library should generate `package.json` when non-buildable. See [spec file](https://github.com/nrwl/nx/pull/29891/files#diff-368467bcd2215def98ef14aaff9dcb056a915b0a724d0eb857f3a0badef8b40a). **Notes:** - Also removed an unsupported `standaloneConfig` option from `@nx/nest:lib` generator. This was removed a long time ago in other generators. - Expo lib generator isn't crystalized when using Rollup for build. This is a separate issue and we'll handle it in another task. ## Current Behavior - Non-buildable Expo libs generate without `exports` - Buildable Expo libs fail to generate due to error - Non-buildable Nest libs do not generate `package.json` ## Expected Behavior Expo and Nest libs generate correct `package.json` files depending on whether they are build or non-buildable. ## Related Issue(s)  Fixes #
1 month ago by FrozenPandaz
Succeeded
20.5.0-beta.1
bc06d63b feat(core): add sync generators option to target defaults in nx-schema (#29441)
1 month ago by FrozenPandaz
Succeeded
20.5.0-beta.0
5721ea3c feat(core): lock graph creation when running in another process (#29408) ## Current Behavior Running Nx in multiple processes at the same time with the daemon disabled can cripple a system due to excess memory usage when creating the graph. This is due to plugin workers being started per-parent process when there is no daemon. This change enables a file lock to prevent the simultaneous processing, and read from the cache when the first run completes. Currently, running `nx show projects` 30 times in parallel looks something like this: 30 processes exited within 37535ms ## Expected Behavior 30 processes exited within 6435ms ## Test Script ```js //@ts-check const { spawn } = require('child_process'); let alive = new Set(); let start = Date.now(); let iterations = 30; for (let i = 0; i < iterations; i++) { const cp = spawn('npx nx show projects', [], { shell: true, env: { ...process.env, NX_DAEMON: 'false', NX_VERBOSE_LOGGING: 'true', }, }); alive.add(i); // cp.stdout.on('data', (data) => { // console.log(`stdout [${i}]: ${data}`); // }); cp.stderr.on('data', (data) => { console.error(`stderr [${i}]: ${data}`); }); cp.on('exit', (code) => { console.log(`child process ${i} exited with code ${code}`); alive.delete(i); }); } const i = setInterval(() => { if (alive.size > 0) { } else { clearInterval(i); console.log( `${iterations} processes exited within ${Date.now() - start}ms` ); } }, 1); ```
1 month ago by FrozenPandaz