blud really forgot order by, and sort, then proceeded to iterate through the array to filter the items into two arrays and finally spread them lmao. great video tho
I think giving the pictures a priority field with an int would have been more useful for the future and not that more complicated. Because than you can "move" the images in whatever order you precisely want. But very nice video showing the awesomeness of SvelteKit i love it too.
At 5:55, shouldn't you run the 2 queries in markPrimary as a transaction, to prevent possible broken state without any primary? e.g. when the DB shuts down or another error occurs right after the first query? 🤔
Do you really want to run invalidateAll? will not rerun all load functions in the tree? I mean it depends on your code but this can lead to massively fetching unnecessary data from the database.
With the Svelte 5 runes, I'm honestly worried. I loved Svelte for its simplicity and even the "magic". Now it feels like any other frontend library to me. They say it's less learning than the current API but I think its quite the opposite. I could instantly jump into Svelt 3/4. But with Svelte 5 runes I had to put effort into learning them and just unhappy with the idea of using them. Granted I see the power and usability of them. Still feel like there could have been a route that kept the charm of Svelte.
That product_image table is super weird. There's nothing preventing several images from being primary from the same product at the same time. Unless there is a specific need, the database schema should be normalized.
I know you said in this video you weren't going to say what features you like about Svelte.kit, and instead would show us by implementing a few features using it, but I'm honestly really interested in hearing what the features you like are. I've started learning the very beginnings of a few different frameworks such as Svelte.kit, Next.js, and Flask, but I don't feel like I know enough to compare them yet. Everyone talks about how amazing Svelte.kit is, which makes me want to commit and deep dive into learning it, but I still don't know what the advantages of Svelte.kit over other frameworks is.
Svelte/sveltekit is way easier to learn for beginners than react/next. It’s syntax is closer to vanilla HTML/JS and the way you set up the client and server for n sveltekit make it easy for a beginner to visualize the relationship between the two. If you’re immediately looking for a job go react/next but I will say JSX can feel cumbersome for a beginner. React isn’t necessarily hard to learn but the concepts and syntax really get away from vanilla HTML/JS
you want to get to market and probably get a job, learn react then leaaarn react then maybe next and then when you are an "expert", learn svelte on your own time, there are no jobs for svelte (pretty much tbh), so yeah, don't follow the hype even PHP is fine and very profitable!
Hey :) I am happy to see people use svelte, it does make more sense to me then other frameworks. There are a couple of things that I dont know how to build yet, maybe you can do a video that I think many people are trying to figure it out. How to authenticate ( just basic, no orm, no ui, just store the jwt in a cookie ) and how to have protected routes. Thank you :) Edited xD, found you'r video ( th-cam.com/video/o7qpw6NeFgw/w-d-xo.html)
I got behind over the last few weeks and have not been looking, I need to catch up. On my end though I can only see the first comment from the creator studio, I generally miss replies and can't really hold any meaningful conversation which is the main reason I started the discord As far as a nextjs implementation, that MIGHT be something we do in the future, at least partially when I get around to trying RSCs
everywhere being page files is really tiring after a while. Esp when some are page.server and some are not. I donno how else can you fix it tho that's how most modern web apps are, just shit tons of pages and components.
Yes but UI libraries and the ready templates are 👎 everything looks very amateurish with svelte. Look at NextUI for react vs Skeleton for svelte... Ugh! (And before anyone say that I can contribute to blabla... No! I'm not an opensource engineer, I'm a user, I use, I don't give back)
I liked skeleton before, but after using it, I realised I can make very bad UIs with it. However, daisyui is really nice I think, and it's framework agnostic
i'd still recommend to learn it, most of the resources and existing online threads will be based on the current version of svelte, not svelte 5, so it's good to be familiar with it. get started now, don't let svelte 5 stop you from learning
blud really forgot order by, and sort, then proceeded to iterate through the array to filter the items into two arrays and finally spread them lmao. great video tho
never heard of orderBy, is it stage 4?
I've been absolutely loving building my SaaS in sveltekit.
The easiest and fastest way to have primary at front would be to swap the primary image with first image, I think.
17:00
You don't need a template string for interpolation in Svelte - you can just use {} in regular string for that
I think giving the pictures a priority field with an int would have been more useful for the future and not that more complicated. Because than you can "move" the images in whatever order you precisely want.
But very nice video showing the awesomeness of SvelteKit i love it too.
At 5:55, shouldn't you run the 2 queries in markPrimary as a transaction, to prevent possible broken state without any primary? e.g. when the DB shuts down or another error occurs right after the first query? 🤔
good call...
Great video! It is nice to see someone else's process with Svelte + Sveltekit. Thanks for making great content
Do you really want to run invalidateAll? will not rerun all load functions in the tree?
I mean it depends on your code but this can lead to massively fetching unnecessary data from the database.
With the Svelte 5 runes, I'm honestly worried. I loved Svelte for its simplicity and even the "magic". Now it feels like any other frontend library to me. They say it's less learning than the current API but I think its quite the opposite. I could instantly jump into Svelt 3/4. But with Svelte 5 runes I had to put effort into learning them and just unhappy with the idea of using them.
Granted I see the power and usability of them. Still feel like there could have been a route that kept the charm of Svelte.
I was going to post the exact same comment about runes
You should create a little project with Svelte 5.
You'll see, it's not much different from Svelte 4.
You should use the fetch wrapper ky. It makes fetch requests so concise.
That product_image table is super weird. There's nothing preventing several images from being primary from the same product at the same time.
Unless there is a specific need, the database schema should be normalized.
A partial unique index can solve this problem easily.
cant start anything in sveltekit because still waiting for svelte 5 to be released 😅
Hey nice video. btw which color and icon theme you are using?
I know you said in this video you weren't going to say what features you like about Svelte.kit, and instead would show us by implementing a few features using it, but I'm honestly really interested in hearing what the features you like are.
I've started learning the very beginnings of a few different frameworks such as Svelte.kit, Next.js, and Flask, but I don't feel like I know enough to compare them yet. Everyone talks about how amazing Svelte.kit is, which makes me want to commit and deep dive into learning it, but I still don't know what the advantages of Svelte.kit over other frameworks is.
Would you recommend learning react and next first for beginners or just go straight to sveltekit ?
Svelte/sveltekit is way easier to learn for beginners than react/next. It’s syntax is closer to vanilla HTML/JS and the way you set up the client and server for n sveltekit make it easy for a beginner to visualize the relationship between the two.
If you’re immediately looking for a job go react/next but I will say JSX can feel cumbersome for a beginner. React isn’t necessarily hard to learn but the concepts and syntax really get away from vanilla HTML/JS
you want to get to market and probably get a job, learn react then leaaarn react then maybe next and then when you are an "expert", learn svelte on your own time, there are no jobs for svelte (pretty much tbh), so yeah, don't follow the hype even PHP is fine and very profitable!
Hey :) I am happy to see people use svelte, it does make more sense to me then other frameworks. There are a couple of things that I dont know how to build yet, maybe you can do a video that I think many people are trying to figure it out. How to authenticate ( just basic, no orm, no ui, just store the jwt in a cookie ) and how to have protected routes.
Thank you :)
Edited xD, found you'r video ( th-cam.com/video/o7qpw6NeFgw/w-d-xo.html)
Ever thought of using superforms? Might be beneficial
So is using adapter static losing full stack capabilities with ts?
Nice, that was seemless!
you look like a happy man when using SvelteKit
Would be nice if you showed how to implement the same thing with next.js and how it is worse. Also why do you not reply to comments :(
I got behind over the last few weeks and have not been looking, I need to catch up. On my end though I can only see the first comment from the creator studio, I generally miss replies and can't really hold any meaningful conversation which is the main reason I started the discord
As far as a nextjs implementation, that MIGHT be something we do in the future, at least partially when I get around to trying RSCs
ever tried to incorporate superforms?
🐐
SvelteKit is the future! 🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉
everywhere being page files is really tiring after a while. Esp when some are page.server and some are not. I donno how else can you fix it tho that's how most modern web apps are, just shit tons of pages and components.
since its only on ide, there are extensions you can use that merge the files in the file tree on the left
otherwise it's pretty confusing
sveltekit + meltui
Good unscripted video showcasing a normal everyday coding task with Sveltekit.
nice web browser.
Do you know which one it is? And/Or what extension use if any?
@@nicosalvo4088 Arc Browser.
Are you sponsored by svelte ? 😅
Nope
Yes but UI libraries and the ready templates are 👎
everything looks very amateurish with svelte.
Look at NextUI for react vs Skeleton for svelte...
Ugh!
(And before anyone say that I can contribute to blabla... No! I'm not an opensource engineer, I'm a user, I use, I don't give back)
I liked skeleton before, but after using it, I realised I can make very bad UIs with it.
However, daisyui is really nice I think, and it's framework agnostic
cant start anything in sveltekit because still waiting for svelte 5 to be released 😅
i'd still recommend to learn it, most of the resources and existing online threads will be based on the current version of svelte, not svelte 5, so it's good to be familiar with it. get started now, don't let svelte 5 stop you from learning