-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix(module-federation): check port availability before starting remote proxies #33871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit a11f8fd
☁️ Nx Cloud last updated this comment at |
…e proxies When multiple MF dev servers run concurrently and share the same remote, they would both attempt to start proxies on the same port, causing EADDRINUSE errors. This fix checks if a port is already in use before attempting to start a proxy. If the port is occupied (likely by another MF dev server that started earlier), the proxy is skipped for that remote since it's already being served. Uses the existing `waitForPortOpen` utility with retries: 0 to perform an immediate check. Fixes #33470
74b1ce8 to
a11f8fd
Compare
…e proxies (#33871) When multiple MF dev servers run concurrently and share the same remote, they would both attempt to start proxies on the same port, causing EADDRINUSE errors. This fix checks if a port is already in use before attempting to start a proxy. If the port is occupied (likely by another MF dev server that started earlier), the proxy is skipped for that remote since it's already being served. Uses the existing `waitForPortOpen` utility with retries: 0 to perform an immediate check. Fixes #33470 (cherry picked from commit 68d539c)
…e proxies (#33871) When multiple MF dev servers run concurrently and share the same remote, they would both attempt to start proxies on the same port, causing EADDRINUSE errors. This fix checks if a port is already in use before attempting to start a proxy. If the port is occupied (likely by another MF dev server that started earlier), the proxy is skipped for that remote since it's already being served. Uses the existing `waitForPortOpen` utility with retries: 0 to perform an immediate check. Fixes #33470 (cherry picked from commit 68d539c)
…e proxies (#33871) When multiple MF dev servers run concurrently and share the same remote, they would both attempt to start proxies on the same port, causing EADDRINUSE errors. This fix checks if a port is already in use before attempting to start a proxy. If the port is occupied (likely by another MF dev server that started earlier), the proxy is skipped for that remote since it's already being served. Uses the existing `waitForPortOpen` utility with retries: 0 to perform an immediate check. Fixes #33470
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
When multiple MF dev servers run concurrently and share the same remote,
they would both attempt to start proxies on the same port, causing
EADDRINUSE errors.
This fix checks if a port is already in use before attempting to start
a proxy. If the port is occupied (likely by another MF dev server that
started earlier), the proxy is skipped for that remote since it's
already being served.
Uses the existing
waitForPortOpenutility with retries: 0 to performan immediate check.
Fixes #33470