test(fixture): improve finding ports to reduce flaky (#55151)
### What Found a flaky test like https://github.com/vercel/next.js/actions/runs/6125719281/job/16628276301?pr=55118#step:29:174, `get-port` throws by port is not available. Peeking bit, there seems an upstream fix hope to improve the situation but unfortunately it happened after get-port switched to native esm only, so bumping is non trivial work. Instead adapting get-port-please as a replacwement but leave get-port as fallback for a while to verify its stability. Once we are certain, we can remove old get-port entirely.
Showing
| ... | @@ -150,6 +150,7 @@ | ... | @@ -150,6 +150,7 @@ |
| "form-data": "4.0.0", | "form-data": "4.0.0", | ||
| "fs-extra": "9.0.0", | "fs-extra": "9.0.0", | ||
| "get-port": "5.1.1", | "get-port": "5.1.1", | ||
| "get-port-please": "3.1.1", | |||
| "glob": "7.1.6", | "glob": "7.1.6", | ||
| "gzip-size": "5.1.1", | "gzip-size": "5.1.1", | ||
| "html-validator": "5.1.18", | "html-validator": "5.1.18", | ||
| ... | ... |
Please
register
or
sign in
to comment