You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i think demoland-web has grown beyond what we originally envisioned it would be a year ago, and it might make sense to upgrade the tech stack a little bit. In particular SvelteKit represents the easiest 'upgrade path' because the entirety of the components can essentially be reused (although we might have to fiddle with imports)
Pros:
(SvelteKit) cleaner management of multiple areas. Right now we are essentially building a different site for each area and then sticking thte files together, which is quite ugly, and also doesn't aid discoverability (if you're on tyne_and_wear, you can't get to isle_of_wight easily). Also this leads to a lot of duplication of static assets (e.g. the demoland-engine wheel) in the built files because the same wheel is being bundled with every area.
(Svelte 5) hopefully cleaner state management, especially in custom scenario creation UI
Cons:
no HMR in Svelte 5 (yet). This isn't a huge deal for me because website loading is quite fast. also, testing custom scenario stuff has often required a hard refresh anyway.
I don't have time to do this for another month 😅
The text was updated successfully, but these errors were encountered:
i think demoland-web has grown beyond what we originally envisioned it would be a year ago, and it might make sense to upgrade the tech stack a little bit. In particular SvelteKit represents the easiest 'upgrade path' because the entirety of the components can essentially be reused (although we might have to fiddle with imports)
Pros:
tyne_and_wear
, you can't get toisle_of_wight
easily). Also this leads to a lot of duplication of static assets (e.g. thedemoland-engine
wheel) in the built files because the same wheel is being bundled with every area.Cons:
The text was updated successfully, but these errors were encountered: