nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
fix/default-plugin-source-map-attribution
Runs and Agents
Timeline
Configuration
Self-Healing CI
Project Graph
Resource Usage
Analysis
Conformance
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(core): make nested integer-like spread errors base-independent The nested IntegerLikeSpreadKeyError only fired when the merge actually reached `mergeObjectWithSpread`. But a pre-`'...'` key the base owns takes the `result[key] = mergeBase[key]` shortcut in `mergeTargetConfigurations` (and the analogous `mergeConfigurations` config-name shortcut), dropping the incoming value without inspection — so a nested `{ '...': …, '<integer>': … }` never reached the throw. With a staging base the authored target threw IntegerLikeSpreadKeyError; when the real base owned the key it did not, so the staging error was discarded and the invalid object silently dropped. Mirror the top-level fix: extract the check into `assertNoIntegerLikeSpreadKey` and run it eagerly at both base-owns-key shortcuts before the incoming value is dropped, so the ambiguity throws regardless of which side owns the key. Also correct the staging comments in `project-configuration-utils.ts`: the discard is safe because throw reachability (not just the condition) is now base-independent, and name refs are skipped because `applySubstitutions` sweeps only the manager's rootMap.
nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte
⌘K
Succeeded
nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte
Click to copy
Linux
4 CPU cores
c1ea4b73
36257
Get faster results
Learn how to enable distribution.
Atomizer enabled
1 group of tasks optimized.