Until this PR is merged all other PRs will fail tests due to wait-on failures.

In draft, pending investigation of new vite version v4.1.3.

The wait-on-vite issue is not resolved by updating to VITE 4.1.3 (latest)

so I suggest to go ahead with this PR.

The log confirms again the issue with GitHub dual definition of localhost.

waiting on "http://localhost:5173" with timeout of 60 seconds
/usr/local/bin/npm run dev

> example-wait-on-vite@2.0.0 dev
> vite


  VITE v4.1.3  ready in 201 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
http://localhost:[51](https://github.com/MikeMcC399/github-action/actions/runs/4224214377/jobs/7334897450#step:3:52)73 timed out on retry 91 of 3, elapsed 90279ms, limit 90000ms
Error: connect ECONNREFUSED 127.0.0.1:5173

1. vite declares it is listening on http://localhost:5173/ Local: http://localhost:5173/
2. GHA says waiting on "http://localhost:5173" with timeout of 60 seconds
3. The error message Error: connect ECONNREFUSED 127.0.0.1:5173 shows that the name resolution leads to pinging on the wrong stack (IPv4 127.0.0.1) instead of IPv6 ::1.

See vite developer's information about stack and name usage depending on Node.js versions vitejs/vite#10638 (comment) which does not tie in to what is observed on GitHub currently.

I resolved the vite issue by changing the startup of vite server to npx vite --host which causes it to listen on all addresses (0.0.0.0).

I had found this workaround some time ago, but I only just located the documentation in Vite Server Options server.host which confirms that it is a supported option.

🎉 This PR is included in version 5.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀