apparently the service worker went bad, fixed it by unregistering

Would be so nice. perf should be compared to the other ways to write an SPA though, not "real RSC"

Made a discussion in the community org, probably a more correct place to bring this up
github.com/orgs/communi...

🤨

Most services lets you create a password and use that instead of facebook. I know I did it with soundcloud some time ago.

My brother helped produced this, it's in norwegian and the refrain is from an old lullaby type song. Really nice

@sebastienlorber.com any chance you've heard of something like this?

*gasp*

yes

Doesn't sound like the hardest thing to make, do bluesky have public available apis?

Most of this is probably because I added the cache property to the setup-node action though. Don't know the build time improvement in isolation as it's been a while since my last deployment so the logs are expired.

That was easy. Total time reported by actions to publish to gh pages seemingly improved by 4-6x

This reminds me I'm still on 2.4 😅 Gonna try this now

This would mean the rules of hooks could get thrown out the window, and stuff like calling hooks conditionally would be possible;

if (whateverEnabled) {
useWhatever();
}

Instead of having useWhatever support an enabled boolean option.

What if the compiler generated id's for hooks you used;

useWhatever()

would become

useIdentifiedHook(generatedId, () => useWhatever())

useIdentifiedHook would give react to identify a hook in another way than call order, but you'd never have to use it yourself explicitly.

open.spotify.com/track/3pfXoh...