Excellent as always. Keep making them and I'll keep watching. Perhaps a short one on setting up SvelteKit with tailwind/daisyUI + (dark/light & theming)
I am so grateful I found your channel. I am trying to upskill with SvelteKit during our company shutdown, and I am just eating up your guide like candy. I think the biggest challenge for me was looking for a UI kit for SvelteKit. I had to try and piece together the how-to setup DaisyUI with SvelteKit, and I found some of the answers in this video. Again, thanks heaps!
😄😁😁I broke everything I built trying the last part, that is nesting the layouts... But hey, what is the fun if you can't break what you build. Awesome examples. In less than 2 hours Svelte-Kit can be mastered by completing Hunter's tutorial. Coming from Vanilla JS world, I first thought Svelte is awesome. Now I have to accept, people using Svelte are more Awesome... 😊😊
I'm new to these layout changes in Svelte and was looking for how to 'opt out' or not use them, e.g. on /login and behold, in 18 minutes I've learned that and so much more. Love the format and delivery, subscribed.
I am really loving your videos. There is a lot of preparation behind them. They are making me save a lot of time, they are clear and straight to the point. 💯 I only have one little feedback, if I may. I understand that removing pauses and keeping videos short is essential to create and keep engagement, but sometimes the speaking feels too quick, at least for me as a non-native speaker. I can "fix" them by pausing, slowing them down, etc., but I find it fundamental that in the most important moments, you take a little pause to let the watcher realize what you are doing. If you also speak a little slower, that would be great. Low-pitch voices are not that great when you set a low playback speed. 😄 In any case, very, very, very good job.
Fantastic video! The biggest takeaway for me is this: "Nesting happens inside slots". It's like Russian Matryoshka dolls. Every +layout must have a somewhere, and every slot contains its own Matryoshka +layout which in turn contains ... Thank you so much!
Hadn't needed to tinker with the new-ish layout structure, disclosure I skipped through ha ha but the 2/3 min there were quite helpful. Thx for your time. Done plenty of these over years, peeps don't get how much time they actually take!!!
Two questions. 1. It looks like you can only do a 'reset layout' inside of a (group). 2. If you have a +layout.js and a +page.js that both have a export load function, then in the +page.svelte does the 'export let data' contain all of the data from +layout.js and +page.js
@@Huntabyte I might be a little late here, but for your example at 3:33, if +page.js also exports an object called user, will it overwrite the user set by +layout.js?
hello Huntabyte, can you please tell me what extension you're using for the files icons? I've downloaded some of them but the folders icons never changed
What is the recommended practice in order to layout auth user/non auth users I've seen a lot of people (and documentation) saying you can handle that from the server hook, but I'm also noticing this is a possible way of handling it. What would you say it is the best in order to have an easier maintainable web?
if you have a load function on the layout at the root, and need to access it in +pages using export data, does this mean you cant have a +page.js file to call another load function? or would it merge all the data from all the load functions in the +page.svelte file?
Hello🎉 I just wonder is it possible for sveltekit to do routing base on Active Theme? For example Themes/ theme-one/ routes/ page.svelte theme-two routes/ page.svelte And then it would find the current page base on active theme. I am planning to build something with sveltekit but currently stuck with the setup
Hey Allen, ensure that you don't have a root route (/+page.svelte) in both the 'routes' directory and the '(app)' directory. If you want the root route (example.com) to have the (app) layout, you will move the root +page.svelte to that directory. Otherwise, you'll need to create an additional route within that (app) directory.
Ok, everything up to layout groups with (app) and (auth)... awesome... brilliant... beautiful... innovative. Everything else after that? Horrible... confusing... useless... unnecessary... a total mess. It gets too segregated and all over the place and complicated.
