“use client only” ?

This is really cool! But did you know that the time you save when you get your cutlery out of the drawer is the same amount of time as the time you lose having to order them when transferring from the dish rack 😜

Do you feel emotions when you see the Runes?

Really appreciate the posts, especially the one about database tables and data for views was very eye opening for me.

I wonder what you think is the benefit of using directives/imports instead a function call like in tanstack starts createServerFn

"Plato relates that Socrates accounts for his seeming wiser than any other person because he does not imagine that he knows what he does not know."

"Web Standards"

But i know thats very different from how the app router works haha, not sure if thats even possible

Yeah, that is true, I guess it what I meant to say is, it would be nice if you opt in to client side only, you can still use the nextjs router features from down there, for example say /dashboard/layout.tsx with client only and all pages and layouts under that would automatically be client only too

Can we add “use client only” directive? For /dashboard pages 😛

Isomorphic SSR mostly, but definitely have a lot of website/app combinations where it would be nice to just have the app part csr only, so you dont have to worry about window not existing etc.. (this happens suprisingly often with third party lib)

Writing boilerplate code. Not all our code is ever DRY