{🧪} +paoloricciuti.svelte
@paolo.ricciuti.me
1.4K followers 430 following 1.8K posts
S1 | Developer | https://sveltelab.dev | Fat guy | Svelte Ambassador 🔶 | Svelte maintainer 🧡 | JavaScript Bender
Posts Media Videos Starter Packs
Join me live in 10 minutes or so! I'm gonna talk about my latest project: a modern way to build MCP servers in TS!
Well well well...how the turntables!
Me sending a discord message, "I still don't get how a framework can have an MPC... to inject docs?"
Mmm how does the code looks like?
Mmm this feels weird...how slow are we talking about? There no component I can throw at the svelte compiler that takes any noticeable amount of time to build
Not really a primitive in the sense of a rune but yeah it will be a primitive in the sense of a couple of utilities from svelte itself that allow you to fetch from an external server 🤟🏻
I wanted to test the Svelte MCP with some local model, but most of them totally sucks at tool call...is there a good ollama local model that is decent at tool call? Also, what client are you using for ollama that supports MCP? I'm using @raycast.com, but I wonder if there's a better one.
We have @dummdidumm.bsky.social and @rich-harris.dev in chains secretly answering all your Svelte prompts...very slow but hella reliable!
Duh probably got a bunch of people hyped

*Svelte MCP
Did you try with the Svelte LLM?
He probably was using the Svelte MCP 😎😎😎
This will technically not break the app in react if you only use count as a dependency...effect is not a good API, is a necessary evil for the one time you actually need to sync with some external system...the problem is that most of the time people use it wrong (also in svelte)
If you can build a minimal repro I can take a look but like this is impossible to tell 😁
Mmm that's weird? Where are you from? We have people all over the world in the maintainers team and it loads super snappy everywhere
different in terms of philosophy, functionality and DX which is why I chose Svelte over it 😊
changes (namely await and remote functions) that we wanted to get out before creating content because they change pretty substantially how you build.

I also think that while on the surface Vue and Svelte are similar (and I would definitely use the former if I could use the latter) they are very
course is definitely something we could try to get out.

In the meantime @joyofcode.xyz definitely has the best information out there, he recently released a deep dive on svelte 5 and it's about to do the same for svelte kit.

Runes also unlocked the ability for us to do some pretty substantial
We are trying our best to document the best that we can in the official docs. I honestly don't see an extreme level of complexity added by svelte 5 but might be because you get quickly used to it.

The frontend master tutorial is there and it's not really updatable but I think having an official
`bind:group` actually never worked across multiple svelte component (and there's probably no way of make it work)...but overall I feel cross component experience is good...what are you missing?
Solid is clearly Noxt and svelte is clearly svext
Going live in 18 minutes or so! Join me and @reinhold.is for This Week in Svelte!

youtube.com/live/P8jdPBK...
I mean...just look at this. Please look at this and tell to my face svelte is not THE best framework. DO IT! 🧡
Fun little interaction challenge: one select changes the options of another, which needs to load data depending on the first.

This is how you do it with the new Svelte APIs. Comfortably fits into one screenshot.
showing this code:

<script>
	import { getStates, getCities } from './data';

	const states = await getStates();
	let selectedState = $state(states[0]);

	const cities = $derived(await getCities(selectedState));
	let selectedCity = $derived(cities[0]);
</script>

<select bind:value={selectedState}>
	{#each states as state, idx}
		<option>{state}</option>
	{/each}
</select>

<select bind:value={selectedCity} disabled={$effect.pending()}>
	{#each cities as city}
		<option>{city}</option>
	{/each}
</select>

<p>Selection: {selectedCity}, {selectedState}</p>