Svelte 5's Secret Weapon: Classes + Context

Рет қаралды 14,448

Ай бұрын

In this video, we'll start with some basic markup and bring it to life using Svelte 5 Runes and other new Svelte 5 APIs. Specifically, we'll be creating a "Toaster" component along with its state that will enable us to push toast notifications from anywhere in our app.
If you enjoy this type of content, please let me know, and I'll gladly create more!
Global State Video: • Global Stores Are Dang...
Starting Code: github.com/huntabyte/svelte-5...
Final Code: github.com/huntabyte/svelte-5...
📁 GitHub: hj.run/github
🌐 Personal Site: hj.run
🚀 Modern SaaS Course: hbyt.us/modern-saas
💬 Discord: hj.run/discord
🐦 X/Twitter: hj.run/x
🖥️ Setup Stuff: hj.run/uses
📃 Topics Covered:
- Svelte 5 Runes
- Svelte 5 $state
- Svelte 5 $effect
- Svelte 5 $derived
- Svelte 5 reactivity
- Svelte 5 classes
- Svelte 5 context
- Svelte context API
- Svelte global state
- Svelte class state
- Svelte reactive classes

Пікірлер: 83

@Huntabyte Ай бұрын

If you're wondering, why not just use a global store and import it into all of your components? Watch this video: kzfaq.info/get/bejne/e990iZiJsczFl5s.html

@laztheripper Ай бұрын

export const state = writable([]); then you just set it client side by checking if (browser) beforehand. this replaces everything you said, and it's way simpler.

@roycrippen9617 Ай бұрын

You've recently come onto my radar in a big way. I had been using shadcn-svelte and bits-ui for months at work and got recommended a video or two of yours and realized I recognized your online alias. Thanks for everything you do for the svelte community. The stuff that you make is great and makes developing svelte applications even more enjoyable.

@Huntabyte Ай бұрын

Hey I appreciate the kind words! Awesome to hear you get to use shadcn-svelte and bits at work!

@ofeenee Ай бұрын

The video’s pace is just perfect! 👌🏼 Well put, well explained, and well done. Thank you so much for making it and sharing it with the community. 🙏

@adriansanchezr.8508 Ай бұрын

While the frontend community keeps moving towards functional components, there's still a bunch of use cases where classes are better suited for, and this is one of them! Great explanation, keep it up! 👏🏻

@cmdeckermusic Ай бұрын

Wow, what a helpful tutorial! I learned so much about Svelte 5 contexts and why you might prefer to set them up with classes. Keep 'em coming!

@Huntabyte Ай бұрын

Glad it was helpful!

@markasena Ай бұрын

Loving these types of content man! more please!

@yunmulu1659 Ай бұрын

What I needed right now. Thanks!

@BhideSvelte Ай бұрын

this type of content really keeps me attach...to svelte, really appreciate your work 😍😍

@kakaique2000 Ай бұрын

Impossible to not fall in love with svelte runes, feels like writing natural javascript but with reactivity and performance

@jeffloucks4071 20 күн бұрын

1. I like this approach 2. I like how many times you said toast

@giannivullo4391 26 күн бұрын

thank you for the great work you are doing here and on the UI libraries you're working on !

@PropelWebDev Ай бұрын

immediately liked. love the consistency of high quality videos! 😊

@Huntabyte Ай бұрын

Thank you!

@alexlatess Ай бұрын

I needed exactly this ! Thx !

@zeroows Ай бұрын

Thank you, please keep them coming

@edwardmanhattan6517 Ай бұрын

i know you frequently do live, but i was worried when you didnt drop any videos for months, now when you do it's bangers after bangers 🔥🔥

@Huntabyte Ай бұрын

The Svelte 5 API being unstable was killing my motivation as I wasn't sure what stuff was gonna be relevant months from then. Now that it's stable I feel much more comfortable!

@MadeInJack Ай бұрын

@@Huntabyte Great to hear, happy to watch your future content! Tips and tricks about Svelte 5 help me a lot!

@greendsnow Ай бұрын

He was busy with developing the best svelte UI library(s)

@johnwu8916 Ай бұрын

Thanks! This is super helpful.

@Nukhtarov Ай бұрын

Awesome. Thanks!

@AB-gx5zj Ай бұрын

Great video, thanks!

@user-lj4lo7cx7m Ай бұрын

Lets go!!

@axeloehrli1148 Ай бұрын

Awesome video!

Ай бұрын

amazing content like always Hunter

@Huntabyte Ай бұрын

Thank you!

@fev4 Ай бұрын

great tip on how to handle the global context

@Loui3Hunna Ай бұрын

Love it!

@user-krnujdp Ай бұрын

Great video, wow!

@lasal7820 Ай бұрын

Awesome!

@MrBaster38 Ай бұрын

Very good video!

@cengytech497 Ай бұрын

Svelte 5 is a beeeast 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥, thanks for informative tutorial

@d4yno 15 күн бұрын

I'd love a video about the snippets you briefly mentioned. Whats the best practice?

@genshian 29 күн бұрын

I dont get why you switched from Next.js to Svelte. You mentioned, to keep things more based in javascript to render out the charts, but I don't understand how Svelte really makes that much easier when you can do that in React. Mostly curious, because I like the separation of js vs. the jsx aspects and if the js is too large I'd just move it into a hook. I guess, I dont know enough about Svelte though.

@good-dev-student Ай бұрын

thank you

@RyoukenDofus Ай бұрын

Nice tutorials ! How about to make a toast showing a loading state when a form is posted and when the reponse is fullfileld show the result? I implemented it using svelte-sooner but 50% of the time it shows a wrong result :c

@mikejohneviota9293 Ай бұрын

I actually use that!! its OVAAAA POWAAAA

@good-dev-student Ай бұрын

❤❤❤❤❤❤❤❤❤

@GriizzDev 16 күн бұрын

Any particular reason you don't just use a singleton pattern with the `getToastState` function? Inside the getter you could check if a ToastState class already exists in context and just return it. If non exists yet, this is the first call, and you create a new ToastState, set it to context, and return it. This way you would not have to consider when to use `set...` and when to use `get...`.

@ratsock Ай бұрын

Does this mean going forward in svelte5 we shouldn’t be using stores in general if runes can extend beyond direct svelte components?

@Hugos68 Ай бұрын

Yes, you probably want to stay away from stores unless you have a specific reason to use them. Runes are more performant and more flexible

@kylerjohnson988 Ай бұрын

To add to Hugo’s already great answer, Runes also provide a consistent reactive model whether you’re in a component or outside of it.

@imho7992 Ай бұрын

Welp new huntabyte vid, time to refactor! 😂

@Huntabyte Ай бұрын

😂

@couragic Ай бұрын

I can’t believe I’m still not subscribed to this channel 😮 FIXED

@sledgex9 Ай бұрын

Why call onDestroy() and clear the Map? Won't the Map be cleared/garbage collected after the class instance gets garbage collected/destroyed? PS: I am mainly a C++ dev, so not too good with object lifetimes in the JS world.

@Huntabyte Ай бұрын

You are probably right on that one. The GC should handle that. Sometimes I get too paranoid and end up taking the trash out myself 😂

@tririfandani1876 Ай бұрын

Any specific reason why you use Symbol instead of just regular string in context?

@Huntabyte Ай бұрын

It's guaranteed to not conflict with any other context in the tree (potentially set by a library that I don't own)

@denverjamesduran2750 Ай бұрын

Hi may I know why not just create a store that multiple components can access? Like just importing the store and mutating it. Whats the difference?

@Huntabyte Ай бұрын

See the video linked in the description about global stores. In a nutshell, if you're building an SPA it's fine. If you're doing any SSR, there is risk of leakage between different users since it is a single object on the server.

@denverjamesduran2750 Ай бұрын

@@Huntabyte thanks a lot for answering. So that's why I get errors like sharing state in server etc even tho I dont have state in my server files Im gonna watch ur video thanks again youre the best!

@afish5581 29 күн бұрын

Helllo, just started with Svelte and worked through the tutorial. There is one chapter about props which does not recommend $props due to performance issues. Since you used them, how big of an issue is it really? Coming from React + TS I prefer the syntax used in this video but I am hesitant to use it.

@Huntabyte 29 күн бұрын

The docs you're referring to are the Svelte 4 docs, which talks about `$$props`, not the single `$props` rune in Svelte 5

@afish5581 29 күн бұрын

Oh 😮 I see. Thx for clarification ❤

@karolus__ Ай бұрын

Why not a toasts store? What is the main advantage using state + context instead of store?

@Huntabyte Ай бұрын

See the video linked in the description. In a nutshell, if you're building an SPA it's fine. If you're doing any SSR, there is risk of leakage between different users since it is a single object on the server.

@karolus__ Ай бұрын

@@Huntabyte interesting! so in context of SSR writable() is long-lived variable on the server even if it's not defined in *.server.ts file and you have to wrap it in context or use $state in svelte 5, I wonder how many people wrapped session in writable store in SvelteKit... 😵‍💫

@omomer3506 Ай бұрын

Hunter you have been missed

@MennoB-sk8tv Ай бұрын

Wouldn’t it be cleaner to only use gettoaststate and there check if there is one in the context and otherwise put one in and return it

@Huntabyte Ай бұрын

This could certainly be done, it depends on if that behavior would be expected or not! In this case, the context needs to be initialized in the layout so that the `` has access to it. I'd rather it fail and throw then silently fail and not know why I have multiple separate toast states floating around!

@theether5993 Ай бұрын

@BonBaisers Ай бұрын

As a senior architect, I will be always amazed how javascript community will always try to avoid a pattern that is easy to learn, efficient and SOLID : dependency injection. We all figured it out long time ago, but still another framework trying to reinvent the weel.

@JackoCribbo 29 күн бұрын

DI and error handling leave me perplexed too, it’s not necessarily a resistance to OOP/SOLID related as functional solutions seem to be snubbed just the same.

@Venyl 23 күн бұрын

I'm not as experienced as you, would you mind elaborating on this comment and explaining how dependency injection would work here?

@BonBaisers 23 күн бұрын

@@Venyl Well the setContext and getContext are literally a service registration and a service getter. Doing that way, is a missed opportunity to me. Why not use interfaces or types in TS to decouple the service implementation and the pages ? Why not get for free lifecycle options ? Why not have a simple file where you can register implementations instead of having them anywhere in the code. Imagine ToastService needs another service, like a NotificationService that can route a notification to Email or SMS, based on another service UserPreferences... you get the point. the setContext getContext pattern can become a nightmare. Testability is another factor.

@rafaelrocha3991 23 күн бұрын

tbh these principles aren’t really opposed to the inversion of control. you can setup the context as a DI container and apply standard principles to it. It’s just an implementation of an IoC container, nothing inherently related to “JS developers”, example check NestJS or Angular if you think JS ecosystem doesn’t have more standard implementation of DI/IoC.

@gageracer Ай бұрын

After learning Context for svelte another friend had an issue with sharing data on his react project so I was like "let's use react context!". Oh boy its not as straightforward as it is in svelte at all. We could not hook it up and gave up on it.

@ppcamps Ай бұрын

I'm with mixed feelings about this svelte 5. It's looking like a lot with React ( I hate react ) But the content is great, btw

@piano42 27 күн бұрын

9:32 this is some very complicated kinda over engineered code... Why don't you store the toasts in a record where the key is the id? Not sure if it's a good idea to mutate the array of toasts. No need to handle a map of timeouts then either...

@Danielo515 Ай бұрын

Having a folder for components, a folder for types, a folder for green things is not going to scale

Ай бұрын

remember this is just an example to showcase the power of svelte5 runes + context, is only to teach on that, not on project folder structure or scalability

@Huntabyte Ай бұрын

@good-dev-student 28 күн бұрын

4 days no new knowledge Master 😢?!

@gageracer Ай бұрын

I love this method and been using it. But I have one issue that I cannot replicate with sveltelab cause it only gives that error on dev mode: When I get the toasts and then pass it as a prop in an each block as `bindable()` to the child, I get an error saying I should use binding lol. It works fine but the error makes me thing I did something wrong. [svelte] ownership_invalid_binding src/lib/components/ContainerSum.svelte passed a value to src/lib/components/Container.svelte with `bind:`, but the value is owned by src/routes/+layout.svelte. Consider creating a binding between src/routes/+layout.svelte and src/lib/components/ContainerSum.svelte

@edwardspresume 28 күн бұрын

for the setTimeout cleanup, would something like this suffice constructor() { onDestroy(() => { this.toasts.forEach((toast) => { clearTimeout(toast.timeoutId); }); }); } addToast(title: string, message: string, durationMS = 5000) { const id = crypto.randomUUID(); const timeoutId = setTimeout(() => { this.removeToast(id); }, durationMS); this.toasts.push({ id, title, message, timeoutId }); } removeToast(id: string) { const toast = this.toasts.find((t) => t.id === id); if (toast) { clearTimeout(toast.timeoutId); } this.toasts = this.toasts.filter((toast) => toast.id !== id); }