feat(client): ping from SharedWorker
Description
No more log spamming with WebSocket connection to * failed: 🙂
I came up with an idea to eliminate the WebSocket pinging in the network tab and the connection error logs and this PR implements that idea.
This PR moves the pinging logic to a shared worker. This makes the connection error log and the network request to be output in a different location (at least for Chrome, haven't checked with other browsers). Except for that, everything should work the same. Since the error log and the network requests won't be output in the (main) devtools, I guess this would reduce the memory consumption.
closes #16361
I noticed that Safari 7-15 does not support Shared Worker 😢 I assumed that it's globally available...
/ecosystem-ci run
📝 Ran ecosystem CI on 78e1551: Open
| suite | result | latest scheduled |
|---|---|---|
| astro | :x: failure | :x: failure |
| vite-environment-examples | :x: failure | :x: failure |
| vitest | :x: failure | :x: failure |
| vike | :x: failure | :x: failure |
:white_check_mark: analogjs, histoire, ladle, laravel, qwik, vite-plugin-react, storybook, vite-plugin-vue, marko, sveltekit, vitepress, waku, quasar, vite-plugin-cloudflare, vite-setup-catalogue, nuxt, vite-plugin-svelte, unocss, vite-plugin-pwa, rakkas, vite-plugin-rsc, react-router, one, vuepress