nxNx
GitHubNxWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      fix/e2e-react-router-reserve-port
    • 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(testing): reserve dev-server ports in the react-router e2e suite Both e2e cases in this suite generated their app without --port, so both took the 4200 default. When the playwright case's dev server had not released 4200 by the time the cypress case's server probed it, the second server relocated to 4201 while Playwright kept navigating to 4200 — "Could not connect to localhost: Connection refused". Two of the three browsers still passed, because the leftover server was serving an identical app until it exited mid-run. Reserve a port per app via reservePort() and pass it as --port, which the react generator threads into both the vite dev server and the playwright config's baseURL/webServer url. reservePort() scans from 6100, outside the framework-default zone, so the reserved ports cannot collide with each other or with a parallel suite on a generator default.
    nx affected --targets=lint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example
Succeeded
c859fc3736585
1%

Potential flaky tasks

2 of 200 tasks retried.

76%

Cache hits

152 of 200 tasks used cache.

89%

Distribution saved time

29m 06s instead of 4h 17m 55s.

Atomizer enabled

7 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools