Eat the mulberries

I have exactly this. It doesn't help. You need, like, a yellow tint to the whole website or something, but even that may not be enough.

No rock stars at the warburg? Seth Meyers obviously never saw Prof. Burnett on his violin

I'm excited to start trying async and remote functions, but might give you guys time to get the ssr side nailed down. Oh, and this transitions bug means I'm having to pin svelte a few releases back anyhow github.com/sveltejs/sve...

The main one for me was the old wanting $state.from or having $effect.pre running on the server. Essentially setting initial state based on page data which is then editable/mutable. I think I'm doing the right thing now by declaring state in a $derived.by or class. The docs are quite terse. ...

A few bumps but happy with where it's heading. Script did a lot of the work at first. That number is exaggerated because there's been some hefty refactoring as well. I have only cursed yours and rich's name a handful of times so that's pretty good!. Maybe paolo's once or twice as well haha

Thanks! Not losing my marbles, good to know. Issue raised github.com/sveltejs/sve...

www.youtube.com/shorts/Wp4EJ...

Now I want to see the movie adaptation that's 'Catch Me If You Can' meets 'Bourne Identity'

In v5 $effect doesn't run on the server so my SSR is broken if I use that. Creating $state in a class works well, but I don't want to make a class for single properties. I think the answer might be to just use a $derived and update it because you can do that.

My issue with syncing state is more like, the initial value of A is derived from page data (e.g. A = data.B + data.C), but then the user can update A once the page is loaded. In Svelte 4 I would have something like $: setInitialValueOfA(B, C) ...

Getting there with runes. Took me a hot second to realise that $effect tracks all state changes, not limited to things referenced in the immediate block like before. Didn't read the docs closely enough.

Moby Dick. Now you have time to play 1 song!

All of this usually just happens in my head, but I'll occasionally let out an Anakin-style "It's working!"

Ah man I get these all the time with prisma when vs-code fluffs the auto-import of enum types. Every time I bang my head against a wall for a few minutes before I remember.

.crew {
background: unknown;
}
.error {
margin: none;
}