nxNx
GitHubNxWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      fix/force-color-propagation
    • 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): 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-cloud record -- nx sync:check
Succeeded
Linux
4 CPU cores
ddc1d79335293

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools