Frontend

Excellent rundown of how data fetching works in SvelteKit – specifically, the relationship between the “rendering tree” (`+layout.svelte` / `+page.svelte`) and the “data tree” (`+layout.server.ts` / `+layout.ts` / `+page.server.ts` / `+page.ts`).

Excellent rundown of how data fetching works in SvelteKit – specifically, the relationship between the “rendering tree” (`+layout.svelte` / `+page.svelte`) and the “data tree” (`+layout.server.ts` / `+layout.ts` / `+page.server.ts` / `+page.ts`).

https://youtu.be/j9Wf_nyKin4

Speaking of which, I really need to revive skiffle.dev one of these days…

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

Definitely! My brother is creating a frame right now and he said to me today that he cannot stand JSX. Skiffle sounds like a solution :)

Amusement, wonder, and uncertainty. now (fcking around), prev @neynar ✴︎ libred.org

Yes!! The implicit parallelization is so handy especially the more deeply nested your routes are.

Ah, and one more due praise for svelte: opt-in parent's load() from a child view is such a simple solution of cascading data. It's nice example of how Svelte is svelte

Good one! +layout.svelte is v useful for modals and transient views. Instead of embedding modal logic within parent page, it's possible to put modal on a different route while keeping +layout state intact. This makes parent view free from modal logic and comes with free perks like component lazy loading

Thank you sharing! I try to watch al that you share.