5 Things I Wish I Knew When I Started Using SvelteKit

Been wanting to make this one for a while, hyped that Svelte 5 is getting closer, there will be so much to talk about...
my stuff
discord: / discord
x (twitter): / bmdavis419
insiderviz: www.insiderviz.com
blok: www.theblokapp.com
timestamps
00:10 Number 1
1:38 Number 2
3:26 Number 3
5:20 Number 4
6:40 Number 5

[@RikunoFilms]

Worth noting that Svelte actually does not "need" the ecosystem react has because it already has it from a decade or two ago. React's ecosystem is so large partially because we needed to take every JS framework people worked in and "wrap" it in React for optimization and compatibility. Svelte does not need wrappers so your vanilla JS libraries just work.

[@bmdavis419]

This is absolutely true, definitely should have called out in the video!

[@MadeInJack]

Could you please do a compressed crashcourse of each feature to clearly distinguish what runs on the client/server (and in which use case you would do each option)? Still struggling 😭 Gotta take the time to go read the full tutorial but a video would be nice too. Thank you!

[@bmdavis419]

Check back on monday :)

[@MadeInJack]

@@bmdavis419 Nice birthday gift actually 🤩

[@MadeInJack]

@@bmdavis419 Nice birthday gift actually! 😄

[@MerkieAE]

I started learning full-stack development in like 2020ish and SvelteKit played a huge role in that. I now use NextJS at my job. All this framework based development really makes me appreciate the client and server model lol. Back when I first started, wrapping my head around what happened on the server vs client was tough. Now I pretty much got it, but I recently had a situation where I had to explain what runs where in NextJS and I had one of those moments where, as I was explaining it, I was thinking "This may be a little too complicated" lol. Also certain components like a table with a search, filter, and sort or even an infinite scrolling feed are easier to code as just client components that do an initial fetch on page load then one on every query update. Idk if this is a grass is always greener situation though

[@FilipeFreire]

Awesome video Ben! I love how SvelteKit is becoming sturdier each day that passes. Definitely my tool is choice for web development right now.

[@s.adnansami5106]

3:51- This is precisely why I love Astro, you can just code in whatever framework you like and even mix-n-match. It resembles the Svelte workflow relatively closely and it does many of the things Svelte is known for as well. It's even got a built in backend for API endpoints and you showed in a recent video how to plug-in Hono.js into those HTTP handler functions very easily(which I am doing for my own project). On a side note, I just love plugging in Hono into the Astro.js backend because it really makes things flexible and in case you need to host your project in a specific way or need to change framework to let's say Next.js, it's very convenient because you don't have to rewrite your backend or modify it much.

[@s.adnansami5106]

If you want to primarily code in Svelte and need to use React packages, Astro is great for that. Makes me wonder why despite this, you don't use it?

[@jitx2797]

yes I really like Astro SSR.

[@bmdavis419]

I do! I have multiple sites in production using Astro

[@strmchsr1537]

You're still saying "lew-see-jah"! 😁I've been working with Sveltekit for months and did NOT know about streaming! 🤯Awesome video.

[@gamingwolf3385]

Hello , ben thank you for this beautiful video , but i have one question , are runes stable to start usingg them , i know they are built as signals like in solid quick so they are really amazing

[@didiercatz]

the API is fairly complete according to the maintainers, but as with any alpha, it's not stable.

[@bmdavis419]

The official responsible answer? No. But that has not stopped me from using them in prod

[@portalteam5832]

Can you do a video analyzing what kind of usage a production app is going to use on something like Vercel? Since there is so much SSR, every page view is a serverless function execution, so how does that use up your quotas?

[@bmdavis419]

Yea, Insiderviz 2 launches next week so once that’s been going for a bit I’ll talk about how we keep costs down (it uses a lot of ssr in sveltekit on Vercel)

[@portalteam5832]

@@bmdavis419 awesome, thanks!

[@s.adnansami5106]

I wonder why you mix arrow function syntax and regular function syntax right at the beginning in the video with the load function file?

[@s.adnansami5106]

ngl, Code inconsistency really gives me OCD.

[@bmdavis419]

I did not even notice that lmao, I really should be better about that

[@nevillebrem]

very cool video!

[@skyhappy]

Your opinion of SvelteKit vs. Nuxt?

[@efimgibsun7969]

Cool

[@boccobadz]

Svelte ecosystem is JS ecosystem, not some weird react-way wrappers without any proper documentation. Compare Apache Echarts and how simple its usage is in Svelte vs its react wrapper which is abysmal.

[@bmdavis419]

Yea I definitely should have mentioned this

[@cbaesemanai]

I picked up svelete kit about a month ago, spent some time with it and wrote a test app. I was loving it right up until I looked at what it took to deploy it. That is where I bailed out, what a mess.

[@bmdavis419]

Really? I've found it to be one of the easiest of the JS frameworks to deploy, NextJS is easy on Vercel, hard everywhere else, but SvetlteKit's adapters make it pretty simple to put anywhere

[@nixoncode]

that you should have stuck with react all along?

[@readywhen]

hihi

[@realitydesigners]

Here’s my 5 things: 1. I should of just used react. 2. I should of just used react. 3. Why didn’t I just use react? 4. I should use react. 5. I’m only using react.

[@bmdavis419]

idk where all this pro-react sentiment is coming from but I generally agree. For me I still prefer sveltekit for a lot of things, but react is feeling better and better, I'm really coming around

[@twd2]

shadcn,Wow 😍😍😍...