Post

Simon Green Kristensen
@simon-green.dev

On the line of "you can just export global state": That might be fine in Svelte CSR, but if you do SSR with SvelteKit, you can't do that. To solve this issue, you either need to drill in props, or use getContext/setContext (which works much like React context providers)

MapleLeaf 🍁
@mapleleaf.dev

svelte 5 is a banger, but people should be careful globalizing states willy-nilly just to share it. you get in situations where you have to do manual state updates / syncs that could be solved by giving the state a scope (declare in a component), where it goes away and reinits with whatever needs it

Ben Holmes
@bholmes.dev

That's a really great point. Oversold the "global" part in this video. And once you get the hang of classes to capture state, it feels like an evolution of hooks to declare component-level state too

Piet de Vries
@piet.eurosky.social

Svelte 5 really feels like Vue 3. And when Vue Vapor fully gets here, I actually don’t see much space for Svelte, because Vue has the bigger ecosystem and solves roughly the same problems in roughly the same way

Ben Holmes
@bholmes.dev

That's a fair take. Love the work Vue is doing, but honestly haven't used the framework much. Also curious: how do the community libraries compare to React? I'm a huge fan of react-aria for accessible UI, but haven't seen a robust equivalent in Svelte at least

Ben McCann
@benmccann.com

I believe that shadcn-svelte is pretty accessibility focused (they built an accessibility library called bits UI to power it). There's a big list of all the UI packages sorted by popularity here: www.sveltesociety.dev/packages?cat...

sveltesociety.devPackages - Svelte SocietyWe are a volunteer global network of Svelte fans that strive to promote Svelte and its ecosystem. As a service to the community, this site is a central index of events, a components directory, as well...
Max
@shipit.dev

The Vapor repo seems to be completely stale for at least a month now. When do you expect it to get "here"? 🤔

Piet de Vries
@piet.eurosky.social

I have no expectations for things like these. Do understand that most big changes usually don’t get build in the open, but get open sourced when in a presentable state, so lack of public commits doesn’t necessarily means it’s actually stale.

Thomas G. Lopes
@thomas.rocks

When using both, they actually feel quite different day to day. I worked with Vue 3, but am quite present on the svelte community, and the dx of both of them is much less similar then you'd expect

Pier
@pierbover.com

Is Vapor going to allow compilation/reactivity outside of components? If not, Svelte still will have an advantage for managing application reactive state IMO. (without the need of bloat like Vuex or Pinia)

Renato Lacerda
@ralacerda.dev

Vue already has reactivity outside of components. In fact, you can use vue reactivity even without vue. But Vapor-mode is going to remove the v-dom, so it'll be similar to how svelte works.

Ben Holmes
@bholmes.dev

I won't mention a thing until I understand it! Been putting it off since usage is fairly low right now. May be the last straw for me to investigate