1. Poor TypeScript Support - especially with Discriminating Unions. (Had to do some crazy hacks, even when I thought it worked, it turns out the intellisense doesn't work well at all when using the components.), Had to change my component API in an unergonomic fashion, and still doesn't work well. I use this pattern everywhere in my design system in React. Even besides this, typing is just very unintuitive. With React just make interface or type and just destructure in function parameter.

2. Doesn't play well with TurboRepo (monorepo) - Apparently, import alias aren't possible with shared UI package and actually need to designate alias in consuming package (but that defeats the point, as the consuming package now needs to reach over its own boundary for type aliasing).

3. Single component per file - https://github.com/sveltejs/svelte/issues/2940, I thought Svelte would reduce LOC, but turns out I have to create an entirely new component file just to store titleMarkup (should only be used by that component). In React, I just assign that simple markup to a variable within the main component. That titleMarkup component, then takes a single prop of title...Title markup too complex to put in main markup, but too simple to keep in its own file. I also had to create another component, if I just wanted to avoid markup duplication based on conditionals (In react, just assign this markup to a variable).

This didn't make me leave, but was a huge pain: Everything being defaulted export. VSCode always takes the default export path. Which is very long. I have to manually switch everything to be a named export so I get short import path.

Shame...really put in over 2 weeks deeply into Svelte. Now I have to be back in React land...Transitions in Svelte are nice though lol