Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Succeeded
master
aa38b256 fix(graph): align exclude flag with others by using findMatchingProjects (#33550)
22 hours ago by pull[bot]
Failed
master
aa38b256 fix(graph): align exclude flag with others by using findMatchingProjects (#33550)
23 hours ago by pull[bot]
Succeeded
master
618c3344 fix(vite): generate .mts config files to force ESM (#33518) Using .mts extension forces files to always be treated as ESM modules, ensuring consistent behavior regardless of package.json or tsconfig settings. This matters for Node 24 because by default Node will strip types from `.ts` files and then they are resolved through normal Node resolution. In the past we can control CJS/ESM through tsconfig options, but now only extension or `type` in `package.json` matters. Changes: - Updated all createOrEditViteConfig calls to pass useEsmExtension: true - Updated normalizeViteConfigFilePathWithTree to check for .mts files first - Updated test files to expect .mts config files - Updated snapshots to reflect new .mts extension Closes NXC-3446
1 day ago by pull[bot]
Failed
master
2dc4cb53 chore(repo): update nx to 22.1.0-rc.5 (#33519) Updating Nx from 22.1.0-rc.3 to 22.1.0-rc.5 --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
3 days ago by pull[bot]
Succeeded
master
e8576a8b docs(angular): update dynamic module federation to use enhanced modules (#33512) This updates the MF dynamic remotes docs for Angular to match new setup. Closes DOC-327
3 days ago by pull[bot]
Failed
master
f54364eb chore(repo): update nx to 22.1.0-rc.3 (#33496) Updating Nx from 22.1.0-rc.2 to 22.1.0-rc.3 --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: FrozenPandaz <FrozenPandaz@users.noreply.github.com>
5 days ago by pull[bot]
Succeeded
master
c1b942fd fix(core): include require paths when resolving specified plugins (#33495) ## Current Behavior Loading local plugins that are relative paths from workspace root, that point to a JS file, still require preliminary data from default plugins despite being resolvable. This is because we aren't passing `paths` to `require.resolve`, so it is trying to resolve relative to the nx package instead of the workspace. ## Expected Behavior The straight JS path resolves ## Related Issue(s)  Fixes #
6 days ago by pull[bot]
Failed
master
a9def426 docs(nx-dev): add monorepo myths article (#32944) Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
6 days ago by pull[bot]
Failed
master
b3e6b03d chore(core): restructure metrics collector for performance and maintainability (#33483) ## Current Behavior The metrics collector has several inefficiencies and architectural issues: - Complex hierarchical data structure (`ProcessTreeMetrics`) that doesn't align with how the data is consumed - Separate `MetadataStore` struct with unnecessary indirection - Full metadata resent to all subscribers on every collection cycle - Mutable parameters passed through collection functions instead of functional return values - Repeated allocations and clones across collection cycles - `CollectionRunner` tightly coupled to NAPI, making it untestable in pure Rust ## Expected Behavior This PR restructures the metrics collector for better performance, testability, and maintainability: ### Architectural Changes 1. **Flat Process Model**: Replaced hierarchical `ProcessTreeMetrics` with a flat `Vec<ProcessMetrics>`, simplifying data flow 2. **Group-Based Organization**: Introduced `GroupInfo` and `GroupType` to logically organize processes: - `MainCLI` - Nx CLI process and its subprocesses - `Daemon` - Nx daemon and its children - `Task` - Individual task execution processes - `Batch` - Batch execution with multiple tasks 3. **Incremental Metadata Updates**: - Track which groups and processes have been sent using `Arc<DashMap<String, GroupInfo>>` and `Arc<DashMap<String, ProcessMetadata>>` - Only send new metadata to subscribers instead of full state every cycle - New subscribers receive full metadata on first update via `needs_full_metadata` flag - Automatic cleanup of dead process/group metadata 4. **Shared State with Arc**: - Metadata maps shared between `ProcessMetricsCollector` and `CollectionRunner` using `Arc<DashMap>` - Eliminated duplicate metadata storage - Single source of truth for all metadata 5. **Functional Programming Pattern**: - Collection functions now return `Result<MetricsCollectionResult>` instead of mutating parameters - Cleaner error handling with `inspect_err` and `map` - Easier to reason about data flow - Removed ~100 lines of code by consolidating logic 6. **Channel-Based Communication**: - Decoupled `CollectionRunner` from NAPI using `crossbeam_channel` - Collection thread sends metrics via channel to listener thread - Listener thread receives metrics and notifies NAPI subscribers - `CollectionRunner` is now NAPI-free and fully testable in pure Rust - Non-blocking collection (subscriber callbacks don't block metrics collection) ### Performance Optimizations - Pre-allocated `Vec` capacity when combining metrics from different sources - Eliminated unnecessary `HashMap` clones during metadata updates - Single-pass insertion into `DashMap` during string key conversion - Reduced memory allocations in hot paths - Collection thread never blocks on JavaScript callbacks ### Code Quality Improvements - **Testability**: Added 7 pure Rust unit tests for `CollectionRunner`: - Group creation with different registration types - Incremental metadata updates - Dead group cleanup - All tests pass without requiring NAPI/Node.js runtime - Clearer separation of concerns between collection and notification - Better comments explaining incremental update strategy - More idiomatic Rust patterns throughout - Updated TypeScript type exports to match new structure ### Threading Model **Before:** ``` CollectionRunner (mixed collection + NAPI notification) ``` **After:** ``` CollectionRunner (pure Rust, testable) └─> Channel └─> Listener Thread └─> NAPI ThreadsafeFunction └─> Subscribers ``` ## Testing - ✅ 241 Rust tests passing (including 7 new `CollectionRunner` tests) - ✅ Native module builds successfully - ✅ TypeScript types updated and exports verified ## Related Issue(s) Part of ongoing metrics collector optimization work.
6 days ago by pull[bot]
Failed
master
1ef26145 docs(nx-cloud): remove references to standalone powerpack (#33471) Updates the Nx Powerpack docs and marketing page to make it clear that Powerpack packages are included with Nx Enterprise, and cannot be purchased separately, and remove references to the Nx Powerpack trial.      --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: Caleb Ukle <caleb@nrwl.io>
7 days ago by pull[bot]
Succeeded
master
0014ae66 fix(gradle): bump gradle migration version (#33479) Ensure that we bump up Nx plugin for Gradle version to 0.1.9 when going from 22.1.0-rc.3
7 days ago by pull[bot]
Failed
master
0014ae66 fix(gradle): bump gradle migration version (#33479) Ensure that we bump up Nx plugin for Gradle version to 0.1.9 when going from 22.1.0-rc.3
7 days ago by pull[bot]
Succeeded
master
9513a1f8 fix(vitest): do not fail when cleanedAngularVersion is of incorrect type (#33436) ## Current Behavior There may be a scenario when `cleanedAngularVersion` is of type `object` rather than `string` which proceeds to error when passed to `semver.major()`. ## Expected Behavior If `cleanedAngularVersion` is not `string`, assume the latest version will be installed. Similar to how no found angular version is handled. ## Related Issue(s) Fixes #33347
9 days ago by pull[bot]
Failed
master
93e0b21d fix(js): update vitest generator import in library generator (#33430) ## Current Behavior The library generator has an unused import and incorrect import pattern for the vitest generator. ## Expected Behavior Clean imports with the correct way to access the configurationGenerator from @nx/vitest. ## Changes - Removed unused imports (logger, readJson) - Updated vitest generator import to use direct require instead of ensurePackage pattern for accessing the generator Fixes #
10 days ago by pull[bot]
Succeeded
master
73ecb304 chore(repo): update nx to 22.1.0-beta.6 (#33423) Updating Nx from 22.1.0-beta.5 to 22.1.0-beta.6
10 days ago by pull[bot]
Succeeded
master
73ecb304 chore(repo): update nx to 22.1.0-beta.6 (#33423) Updating Nx from 22.1.0-beta.5 to 22.1.0-beta.6
10 days ago by pull[bot]
Succeeded
master
685e497c feat(vitest): split vitest into @nx/vitest plugin (#33311) Split `vitest` out of `@nx/vite` and create a new `@nx/vitest`. This allows for each plugin to have a single responsibility. One for bundling, one for testing. It should allow for lighter setups where Vite for Bundling is not required, but users still want to use vitest for testing. --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: Coly010 <Coly010@users.noreply.github.com>
10 days ago by pull[bot]
Succeeded
master
373066a3 feat(core): track system metrics and link plugins to workers when possible (#33411) - Track relevant CPU and memory system metrics. - Link plugins to workers when possible. - Refactor collector code by splitting it into two separate structs.
13 days ago by pull[bot]
Failed
master
746b89a9 feat(maven): bump version from 0.0.8 to 0.0.9 (#33405) ## Current Behavior Maven plugin is currently at version 0.0.8. ## Expected Behavior Maven plugin should be bumped to version 0.0.9 with a corresponding migration for users. ## Changes Made - Updated parent POM version to 0.0.9 - Updated package.json version to 0.0.9 - Updated mavenPluginVersion constant to 0.0.9 - Added new migration (0-0-9) to update user pom.xml files from 0.0.8 to 0.0.9 - Scheduled migration for Nx v22.1.0-beta.6 ## Testing - ✅ Maven package tests pass - ✅ Build succeeds - ✅ Linting passes
13 days ago by pull[bot]
Succeeded
master
a6948665 fix(core): correctly identify local workspace dependencies on windows (#33408)
13 days ago by pull[bot]