Daniel Tschinder

This is already fixed on the main branch and the warning will disappear with the next version of the cli.

> Error: listen EADDRINUSE: address already in use :::\ ~~Windows & Mac When this happens it happens a couple of times in a row.~~ ~~https://github.com/netlify/cli/runs/6597781685?check_suite_focus=true https://github.com/netlify/cli/runs/6597696852?check_suite_focus=true~~ Done

> wasm streaming compile failed: TypeError: Failed to parse URL from /Users/runner/work/cli/cli/node_modules/netlify-redirector/lib/redirects.wasm␊ falling back to ArrayBuffer instantiation␊ › HTTPError: Response code 503 (Service Unavailable)`, ~~https://github.com/netlify/cli/runs/6597695768?check_suite_focus=true~~ ~~In progress: Updating netlify-redirector.~~

~~yarn → should install the cli and run the help command~~ ~~✖ Timed out while running tests~~ ~~https://github.com/netlify/cli/runs/6598249957?check_suite_focus=true~~ ~~#4637~~ Done

> EBUSY: resource busy or locked, rmdir ... Windows https://github.com/netlify/cli/runs/6612669436?check_suite_focus=true

> Error: EPERM: operation not permitted, rename 'C:\\Users\\runneradmin\\AppData\\Roaming\\netlify\\Config\\config.json.3515056301' -> 'C:\\Users\\runneradmin\\AppData\\Roaming\\netlify\\Config\\config.json'`, Windows https://github.com/netlify/cli/runs/6612669436?check_suite_focus=true

Closing, it is a lot better now, and we should handle the ones that come up.

This is fixed with #4998 Once the next release is published it will go away.

Thank you for reporting this. We are aware of some smaller performance issues (#349) but not to that extend. I tried to reproduce this, without success so far. - Is...

There is also a PR for this (or at least parts) already: https://github.com/netlify/cli/pull/4553