NxEnterprise
    Nx
    fix(core): preserve FORCE_COLOR=0 intent for forked child tasks When FORCE_COLOR=0 is set in the environment, bin/nx.ts deletes it (workaround for picocolors treating '0' as truthy). However, task-env.ts and task-orchestrator.ts then default the undefined FORCE_COLOR to 'true' for all forked children, re-enabling ANSI colors. Save the original FORCE_COLOR value in NX_ORIGINAL_FORCE_COLOR before deleting, and consult it when building child process environments. Extract the logic into a shared getForceColorForChild() helper. Fixes #35292 Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d8c4e-0d90-7126-b438-be77211ef603
    nx affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run
Sign in / Sign up
Succeeded
CI Pipeline Execution

nx affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run

Click to copy
read access token used
ddc1d79335293
76%

Cache hits

550 of 724 tasks used cache.

90%

Distribution saved time

12m 21s instead of 1h 58m 28s.

Atomizer enabled

47 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools