Conduitry
Conduitry
I can't reproduce this in Safari 14. I suspect it was a server or network glitch, unrelated to the browser being used. Are you still seeing this in Safari?
As far as I can tell, there are two places where this specific issue could be attacked. I think they would both be reasonable new features for the REPL, but...
I'm not seeing this on Node 17.7.2. It works fine for me.
I've just tested this again on a fresh Windows 10 sandbox, Node 16.13.2, and cannot reproduce it.
Transferring this to the REPL repository, although I'm not sure what we could reasonably do to resolve this. Maybe monkeypatch/inject our own copies of `setTimeout`/`setInterval` that internally note somewhere the...
https://github.com/sveltejs/svelte/issues/7196 brought up the same sort of issue with `requestAnimationFrame`, and I'm not sure how to best handle that, either.
Is the suggestion here that the `+page.js` function would get a synthetic `FormData` object and would then be responsible for making whatever underlying request is appropriate? I'm not sure how...
If anyone has a minimal reproduction, that would help immensely. There's not much to glean from a video of an app whose source we cannot see.
This is not the correct way to be using `read()`, although it doesn't look like we're documenting this well currently, as far as I can tell. `read()` should be passed...
@eltigerchino solicited opinions about this in the maintainers' chat, and my opinion (which I see @PatrickG also commented with above) was that we should instead serialize the server `load` function...