Client runtime uses `Promise.withResolvers`, which needs Safari 17.4

[Nic-Polumeyv]

Describe the bug

The remote functions client code calls Promise.withResolvers() in query/instance.svelte.js and query-live/instance.svelte.js. That needs Safari 17.4 / Chrome 119 / Firefox 121, but Vite 8's default target is Safari 16.4 / Chrome 111 / Firefox 114 and APIs aren't polyfilled, so remote functions throw on Safari 16.4-17.3. Replace with a plain executor, or document the higher floor? I'll PR the former if that's the call.

Reproduction

Code inspection, so no repo:

• https://github.com/sveltejs/kit/blob/e76b3d778076af8ba1d245e1c1f39917e3d3711c/packages/kit/src/runtime/client/remote-functions/query/instance.svelte.js#L103
• https://github.com/sveltejs/kit/blob/e76b3d778076af8ba1d245e1c1f39917e3d3711c/packages/kit/src/runtime/client/remote-functions/query-live/instance.svelte.js#L81 (also L124, L355)

The built client bundle ships the calls verbatim; any app using remote functions on those browsers hits it. Old Safari can't be demonstrated in a hosted repro anyway.

Logs

No response

System Info

version-3 @ e76b3d77, vite ^8.1.5 (default build.target)

Severity

serious, but I can work around it

[teemingc]

Related: we've defaulted to unbundled service workers which is only recently supported by Firefox https://caniuse.com/wf-js-modules-service-workers

[Nic-Polumeyv]

Firefox only shipped module service workers in 147, this January, so that floor is even higher than this one (Firefox 121). withResolvers is a four-line executor swap so I'd fix it either way, but the service worker one is structural since #16169. If the position is that v3 targets current Baseline rather than Vite's default target, that belongs in the docs and this becomes a docs change.