Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/default-plugin-source-map-attribution
- Runs and Agents
- Timeline
- Configuration
- Self-Healing CI
- Project Graph
- Resource Usage
- Analysis
- Conformance
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Sign in

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 affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example

Succeeded

c1ea4b7336257

88%

Cache hits

540 of 617 tasks used cache.

50%

Distribution saved time

16m 51s instead of 33m 44s.

Atomizer enabled

48 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools