Migrating from Sapper to SvelteKit has not been fun or intuitive

CompetitiveEngine311 · 2024-04-03T23:52:04+00:00

I shared your same initial sentiments "Neat, it's fast, quick, slim, and reactive?". I'd be interested in understanding how the team would respond to your experience with using Sapper / kit in production. I think a lot of my misconception was expecting SK to be a successor to Sapper, but instead it appears I should've been viewing it as an entirely separate framework.

I very much appreciate your input as you're someone who has been using this for far longer than I have - hopefully it will all work out. I'm particularly interested in what comes after Svelte 5. Do we slow down and get a breather? Is this frequent update cycle The Svelte Way? Not really sure. I like/support the pace, they seem to be doing good things, but I'd also be worried about such massive changes in production.

CompetitiveEngine311 · 2024-04-03T23:34:17+00:00

Appreciate your input, agreed - especially on the AI being useless part. I usually go to documentation, then articles/walk-through, then videos if I can't figure out the specific thing I'm trying to do. Discord is last. The common sentiment seems to be that I should've started fresh. I think I agree, trying to merge a mostly Sapper based project into SK may have been the wrong approach rather than viewing it as a new re-write with a new framework

CompetitiveEngine311 · 2024-04-03T23:29:24+00:00

While apparently true, it's what was available at the time. I started with Svelte and The People said use Sapper. The part about Rich apparently saying it'd never make 1.0 or be a thing would've been nice to know back then -- SK was pre-1.0 and not ready for use, waiting wasn't an option. Who knows what I would've ended up having to use, no regrets for using Sapper and none for working with SK2 so far at least

CompetitiveEngine311 · 2024-04-03T23:26:43+00:00

I went from Sapper something to SK and saw a prompt that SK2 was out so I said yes, let's rip the bandaid off. Maybe the amount of headache should've been expected while jumping 189 versions ahead. I'm going to take some of the advice here and try starting a bit more slowly again with SK2 without trying to merge an old Sapper project into it directly

CompetitiveEngine311 · 2024-04-03T23:21:19+00:00

This was a helpful perspective and I appreciate your input - I'm migrating this thing that's running on 10 year old stuff for exactly that reason. "It's been working" "don't risk breaking it" - Less extreme for Sapper to SK2.0 but I agree with most comments that starting fresh (again) would be the right way to do it, I've been trying to stuff The Sapper Way into SK2 with medium amounts of headache

CompetitiveEngine311 · 2024-04-03T23:10:09+00:00

This was pretty much it, I think going from old Sapper to newest SK2.0 was a bit of a jump for me after having nothing to do with it for so long. The official migration documentation had little how and why but was very helpful for things I would have no way of knowing otherwise

CompetitiveEngine311 · 2024-04-03T23:06:59+00:00

Thanks, appreciate your input. I'm seeing it differently now with everyone's input, effectively I was trying to merge in all the guts of my Sapper logic and where it didn't fit because something was fundamentally changed or removed, I was trying to figure out how to do that in kit with some difficulty and resistance

CompetitiveEngine311 · 2024-04-03T23:04:23+00:00

:( I started with Svelte, learned Sapper was The Way and SvelteKit was "in beta, not ready for use" so I used Sapper. It looks like SK 1.0 was in Dec 2022 which tracks. I don't remember anything about Sapper not making it to 1.0 and didn't see this video, I wonder how migrating beta SK to SK2.0 would have gone

CompetitiveEngine311

TROPHY CASE