nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
fix/e2e-react-router-reserve-port
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(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 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
c859fc37
36585
Get faster results
Learn how to enable distribution.
Atomizer enabled
1 group of tasks optimized.