Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
34160
9a96368f Merge branch 'master' into support-plugin-project-negations
3 hours ago by llwt
Failed
34160
Environment issue→
546fd2b1 feat(core): optimize pattern matching by checking negations once Refactor pattern matching to check for negation patterns once upfront instead of on every file iteration. Creates specialized matcher functions that eliminate null checks and branching in the hot loop. Changes: - Split into matchesSimplePatterns (fast) and matchesNegationPatterns (full) - createIncludeMatcher() returns function that always returns true if empty - createExcludeMatcher() returns function that always returns false if empty - Eliminates null checks and conditional logic in the file iteration loop - Matchers created outside the file loop in findMatchingConfigFiles Performance impact (1500 files, 4 patterns): - Before: 32.1ms (checking negation per file) - After: 26.0ms (checking negation once) - Improvement: 19% faster 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
7 days ago by llwt
Canceled
34160
372a3ca3 feat(core): add fast-path optimization for plugin include/exclude patterns Add a fast path for pattern matching when no negation patterns are present. This maintains backward-compatible performance while supporting the new negation pattern feature. Performance impact (1500 files, 4 patterns): - Non-negation patterns: 18% faster than before (26.8ms vs 32.7ms) - With negation patterns: Acceptable overhead for new feature (23.6ms) The fast path uses short-circuit evaluation (.some()) which exits early on first match, while the slow path processes all patterns sequentially to handle negation logic correctly. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
7 days ago by llwt
Canceled
34160
499e4e70 docs(nx-dev): document negation pattern support for plugin include/exclude Add documentation for the newly added negation pattern feature in plugin include/exclude configuration. Includes examples and explanation of how the patterns are processed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
7 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
11 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
12 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
12 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
12 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
12 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
12 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
13 days ago by llwt
Succeeded
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
13 days ago by llwt
Failed
master
88098cc5 fix(core): ensure consistent yarn optional dependency hashing (#34104) ## Current Behavior For optional packages that are not installed when using yarn, we currently add the package version to the key for the hash. NPM and PNPM do not do this. The results in inconsistent hashes for package dependencies when running in different environments. For example, trying to use the cache created in CI on linux on a mac where native dependencies are used. **yarn on arm mac** _note how the key has the version in it for the linux and x64 versions that are not installed_ ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64@22.3.3": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu@22.3.3": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ``` **npm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-darwin-arm64": "1683411334940043113", "9980946580833020728", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` **pnpm on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-arm64": "1683411334940043113", "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", ``` ## Expected Behavior Optional dependencies should be handled the same way from a hashing perspective as installed dependencies. **yarn on arm mac** ``` $ nx test foo | grep @nx/nx- ... "npm:@nx/nx-darwin-x64": "14042642002999097748", "npm:@nx/nx-linux-x64-gnu": "12169496858981304476", "npm:@nx/nx-darwin-arm64": "1683411334940043113", ```
13 days ago by llwt
Succeeded
34104
0a6a80fa Merge branch 'master' into fix-hashing-optional-yarn-dependencies
13 days ago by llwt
Canceled
34104
0a6a80fa Merge branch 'master' into fix-hashing-optional-yarn-dependencies
13 days ago by llwt
Failed
34104
Fix rejected→
78677def fix(core): ensure consistent dependency hashing for yarn with optional dependencies
13 days ago by llwt
Succeeded
679
284a5add fix(schematics): use correct action type for LoadError The `LoadError` action was mapped to the `Load<%= className %>` action type rather than `<%= className %>LoadError`.
1 month ago by llwt