It's likely something to do with the experimental nature -- if you can narrow it down and file a bug (to kit or svelte, whichever it ends up being) we'd love it!
November 13, 2025 at 9:37 PM
It's likely something to do with the experimental nature -- if you can narrow it down and file a bug (to kit or svelte, whichever it ends up being) we'd love it!
Ouch, that's painful. I had some heartburn upgrading an app from Svelte 4 to Svelte 5 as well. Thankfully it was just like... half a day of painful boring work
November 13, 2025 at 9:36 PM
Ouch, that's painful. I had some heartburn upgrading an app from Svelte 4 to Svelte 5 as well. Thankfully it was just like... half a day of painful boring work
Yeah, it’s treeshaking. They should be able to remove this code, but they don’t.
November 12, 2025 at 5:07 PM
Yeah, it’s treeshaking. They should be able to remove this code, but they don’t.
Yeah rollup has the best treeshaking we’re aware of and rolldown isn’t far behind.
November 12, 2025 at 2:01 PM
Yeah rollup has the best treeshaking we’re aware of and rolldown isn’t far behind.
Don’t forget Apple Music / App Store!
November 8, 2025 at 10:02 PM
Don’t forget Apple Music / App Store!
Just Say No to platforms with backslash path delimiters
November 5, 2025 at 5:57 PM
Just Say No to platforms with backslash path delimiters
Even cooler, if you don't use the clsx syntax, you don't end up with clsx as a dependency. 100% value if you want it, 0% cost if you dont
November 3, 2025 at 7:27 PM
Even cooler, if you don't use the clsx syntax, you don't end up with clsx as a dependency. 100% value if you want it, 0% cost if you dont
JSDoc has significant benefits (no build step being the primary one), but its unreadability and verbosity are strong marks against it. In any context where I already have to have a build step (eg working on webapp that needs to run through something like Vite/rollup), I'm always picking TypeScript.
October 27, 2025 at 3:32 PM
JSDoc has significant benefits (no build step being the primary one), but its unreadability and verbosity are strong marks against it. In any context where I already have to have a build step (eg working on webapp that needs to run through something like Vite/rollup), I'm always picking TypeScript.
...to the process of software development. TypeScript's benefit has way, way outweighed its negatives.
As someone who spends all day, every day working on a JSDoc codebase, getting to write regular TS syntax is a breath of fresh air. The JSDoc version is just so, so ugly and annoying to write.
As someone who spends all day, every day working on a JSDoc codebase, getting to write regular TS syntax is a breath of fresh air. The JSDoc version is just so, so ugly and annoying to write.
October 27, 2025 at 3:31 PM
...to the process of software development. TypeScript's benefit has way, way outweighed its negatives.
As someone who spends all day, every day working on a JSDoc codebase, getting to write regular TS syntax is a breath of fresh air. The JSDoc version is just so, so ugly and annoying to write.
As someone who spends all day, every day working on a JSDoc codebase, getting to write regular TS syntax is a breath of fresh air. The JSDoc version is just so, so ugly and annoying to write.
Inline type definitions are never going to be enough for all of your documentation needs. Saying TypeScript was a mistake is a huge overstatement. With the benefit of hindsight we might be able to say "Hey, this would've been better if it'd been a comment-based syntax," but that's just not fair...
October 27, 2025 at 3:30 PM
Inline type definitions are never going to be enough for all of your documentation needs. Saying TypeScript was a mistake is a huge overstatement. With the benefit of hindsight we might be able to say "Hey, this would've been better if it'd been a comment-based syntax," but that's just not fair...
everything is the reactive graph, and the reactive graph is everything
October 27, 2025 at 3:25 PM
everything is the reactive graph, and the reactive graph is everything
setInterval with an invalidate call seems pretty reasonable, yeah
October 26, 2025 at 9:30 PM
setInterval with an invalidate call seems pretty reasonable, yeah
Keep it up!! We absolutely love the community and couldn’t even come close to maintaining it without the massive grassroots efforts that go into every meetup and community library.
October 25, 2025 at 6:43 PM
Keep it up!! We absolutely love the community and couldn’t even come close to maintaining it without the massive grassroots efforts that go into every meetup and community library.
Really disappointing so far. I loved Biome when I first tried it but their plugin architecture has left a lot to be desired and the most recent “full support for svelte! (Except not at all in any way)” announcements leave a bad taste in my mouth.
October 25, 2025 at 6:41 PM
Really disappointing so far. I loved Biome when I first tried it but their plugin architecture has left a lot to be desired and the most recent “full support for svelte! (Except not at all in any way)” announcements leave a bad taste in my mouth.
please, show me the hydration comments this generates 😂
October 22, 2025 at 8:59 PM
please, show me the hydration comments this generates 😂
I think you'd just use this: svelte.dev/docs/kit/pag...
You might also have to provide custom entries to get SvelteKit to actually call the endpoint with all of your blog slugs during prerendering, as it wouldn't find them during crawling:
svelte.dev/docs/kit/pag...
You might also have to provide custom entries to get SvelteKit to actually call the endpoint with all of your blog slugs during prerendering, as it wouldn't find them during crawling:
svelte.dev/docs/kit/pag...
Page options • Docs • Svelte
Page options • Svelte documentation
svelte.dev
October 8, 2025 at 6:04 PM
I think you'd just use this: svelte.dev/docs/kit/pag...
You might also have to provide custom entries to get SvelteKit to actually call the endpoint with all of your blog slugs during prerendering, as it wouldn't find them during crawling:
svelte.dev/docs/kit/pag...
You might also have to provide custom entries to get SvelteKit to actually call the endpoint with all of your blog slugs during prerendering, as it wouldn't find them during crawling:
svelte.dev/docs/kit/pag...
I'd be surprised if you couldn't prerender your OG images, which would bypass the cold start issue... have you tried this?
October 8, 2025 at 4:41 PM
I'd be surprised if you couldn't prerender your OG images, which would bypass the cold start issue... have you tried this?
It’s not “done done” — I’m currently working on “hydratables/resources” that allow you to inline the results of data fetched on the server into your HTML so that it can hydrate synchronously. Remote Functions already do this, though, so if you’re using SvelteKit, async SSR “just works”.
October 7, 2025 at 5:41 AM
It’s not “done done” — I’m currently working on “hydratables/resources” that allow you to inline the results of data fetched on the server into your HTML so that it can hydrate synchronously. Remote Functions already do this, though, so if you’re using SvelteKit, async SSR “just works”.
fwiw I wrote the interface so feel free to ping with questions if you run into them — I’m not super active on social media but I’ll see them eventually! 😂
October 6, 2025 at 4:10 AM
fwiw I wrote the interface so feel free to ping with questions if you run into them — I’m not super active on social media but I’ll see them eventually! 😂
This is the same strategy Vercel’s AI SDK has for the framework-agnostic Chat interface. Go check out the Svelte implementation in that repo if you want more reference.
October 5, 2025 at 1:27 AM
This is the same strategy Vercel’s AI SDK has for the framework-agnostic Chat interface. Go check out the Svelte implementation in that repo if you want more reference.
Interesting; I get the same result from Wappalyzer but I can't figure out what's actually using Svelte on the page...
October 1, 2025 at 7:22 PM
Interesting; I get the same result from Wappalyzer but I can't figure out what's actually using Svelte on the page...