gentle warren
It worked a long time, and now it suddenly stopped working. Not sure what exact change caused it to stop. Running on remix-run/* 2.1.0 and wrangler 3.14.0.
Generally asked, which steps could I take in order to track down the root cause? When I change a file, I can see that stuff is rebuild, that the socket receives information (console.log) – just no live refresh happening.
abstract spire
i've seen others report that reverting to an older version of wrangler worked something like 3.10 or 3.11
gentle warren
Thanks for the tip, but unfortunately it doesn't help... only with remix 1.19.3 I was able to get it working up to wrangler version 3.10 (had somewhere an old sample project).
Using a fresh pages/workers installation (with create-remix) nothing did work, went back to wrangler 3.1 :/
abstract spire
man that's frustrating... we're working full steam ahead on the Vite stuff right now and working with CF core team to deliver best-in-class DX for that. we'll see if there anything we can do short-term to make the DX better for you with the current compiler, but rest assured that when the Vite stuff lands w/ CF support its going to be way better
gentle warren
thank you! I had it working for a long time. Checked on another macbook, and got it working there with a fresh install of remix 2.1 but with wrangler 3.8. Couldn't replicate this on my main machine though. The only difference I can think of is different OS version (main is 14, side is 13.1) – but I'm not sure if this could have that much of an impact.
I'll keep trying, maybe somebody has some tips what to look for. Until then I'll wait for the vite update and stick to good old manual refresh 😉
abstract spire
Yea unfortunately getting CF to work reliably with wrangler v3 and the new workerd env it runs on has been finicky. But that's why we're working directly with CF core team now!
opal drum
I have the same issue, for the time being I added --live-reload to wrangler, but I don't think this is a permanent fix to it.
"start": "wrangler pages dev --live-reload --compatibility-date=2023-06-21 ./public",
@abstract spire that's great news! Hope that these issues are gone soon. Btw I got it back working, but only for very small updates (sometimes requires an initial refresh). For busy components or routes that uses streamed data, it still won't work. So, almost all 😅 unfortunately
@opal drum haven't tested that, but seems hacky :/ also I had to switch to workers because pages doesn't support wrangler.toml (well partly, which makes it even more annoying) as well as queues. And I don't want to use another worker just for that :/
maybe that is what devServerBroadcastDelay used to solve