00:00:00 Stream Starts 00:26:00 What is SolidJS? 00:34:49 What is SolidStart? 00:46:34 Browsing Source Code of Hacker News Clone 01:33:20 Building a Pokedex 03:00:52 Opening Pokemon Cards
Thanks for the stream. It definitely helped me understand gaps in documentation and the way we present examples. I'm glad you did figure it out in the end. To your question of the purpose of the `load` function.. it is mostly to handle preloading for like link hovers on the client and single flight mutation. Everything is always server rendered in the examples and if it isn't available at first it streams in afterwards. 1. We fetch data on the server and realize it isn't ready to stream yet, we stream the shell 2. Data resolves, we finished rendering the HTML on the server for that part of the page and stream it and the serialized data with it. 3. Client component hydrates it gets the stream data that was serialize and hydrates that part of the page. In so you would see the data console.log on both client and server. Both when the server renders the HTML after it resolves the data, and on the client when it hydrates. But the content on the pages is server rendered(and fetched) just streams in as it is available.
Oh wow!! Thanks for watching. I don't know if my confusions will be the same with everyone, but that definitely clears things up! It was hard for me to break the mental model of the load function in SvelteKit. It's good to know that everything is SSR by default. I guess me seeing the console.log on the client made me think it was requesting the data there, but in the case of SSR it was just logging already hydrated data.
btw while watching, little note: the suspense was in the metaprovider, because if any route-file changed and has a Component from the (at)solidjs/meta it will display it correct. + the suspense allows for a fallback bucket for loading async stuff (createAsync) :D
Glad I'm not the only one who is confused by the whole load/data fetching on route load paradigm. Feel like you need to have a PhD in order to understand how to use it correctly. Apart from that SolidJS is a great choice but I really don't like the whole load thing..
I don't have one planned, but I hope to keep working on this app soon. Keep an eye on the discord and mailing list for go live notifications: list.coding.garden/ coding.garden/discord/
They really need to sort out the adds on twitch every 10 mins you appear to get one, hopefully the experience here is better, fell asleep watching the stream
![Six Hundred Strike [EPIC: The Musical] Full Animatic](http://i.ytimg.com/vi/zov6NXIAuow/mqdefault.jpg)
00:00:00 Stream Starts
00:26:00 What is SolidJS?
00:34:49 What is SolidStart?
00:46:34 Browsing Source Code of Hacker News Clone
01:33:20 Building a Pokedex
03:00:52 Opening Pokemon Cards
Thanks for the stream. It definitely helped me understand gaps in documentation and the way we present examples. I'm glad you did figure it out in the end.
To your question of the purpose of the `load` function.. it is mostly to handle preloading for like link hovers on the client and single flight mutation. Everything is always server rendered in the examples and if it isn't available at first it streams in afterwards.
1. We fetch data on the server and realize it isn't ready to stream yet, we stream the shell
2. Data resolves, we finished rendering the HTML on the server for that part of the page and stream it and the serialized data with it.
3. Client component hydrates it gets the stream data that was serialize and hydrates that part of the page.
In so you would see the data console.log on both client and server. Both when the server renders the HTML after it resolves the data, and on the client when it hydrates. But the content on the pages is server rendered(and fetched) just streams in as it is available.
Oh wow!! Thanks for watching. I don't know if my confusions will be the same with everyone, but that definitely clears things up! It was hard for me to break the mental model of the load function in SvelteKit.
It's good to know that everything is SSR by default. I guess me seeing the console.log on the client made me think it was requesting the data there, but in the case of SSR it was just logging already hydrated data.
I used solid start since 0.3.x and am very happy how it turned out, 1.0.0 is incredibly well made
btw while watching, little note: the suspense was in the metaprovider, because if any route-file changed and has a Component from the (at)solidjs/meta it will display it correct. + the suspense allows for a fallback bucket for loading async stuff (createAsync) :D
Glad I'm not the only one who is confused by the whole load/data fetching on route load paradigm. Feel like you need to have a PhD in order to understand how to use it correctly. Apart from that SolidJS is a great choice but I really don't like the whole load thing..
It's painful to watch you try to learn solid and solidstart at the same time 😅
Damn it I missed the stream. We know when the next one is?
I don't have one planned, but I hope to keep working on this app soon. Keep an eye on the discord and mailing list for go live notifications:
list.coding.garden/
coding.garden/discord/
They really need to sort out the adds on twitch every 10 mins you appear to get one, hopefully the experience here is better, fell asleep watching the stream