> when is your training cutoff gpt 5.2: My training data goes up to August 2025 > write a valid svelte 5 component see photo. it did decent. two issues: `on:click` and passing a fn to $derived()

svelte.dev/docs/svelte/... has 30 lines with trailing whitespace

svelte-streamdown adds >15mb (!!) to bundle size. Any advice on alternatives? github.com/beynar/svelt...

svelte's a11y onclick warning causes ai to add role="button". I deployed that change and several blind users reached out complaining that their screen reader started failing them.

apps.apple.com was rewritten in svelte ⚡🧡

> no Svelte config found at ... using default configuration any way we can silence this error? please? :)

Thanks for the tip. Much better dx. And shaved 85kb off my svelte bundle size (moved from paraglide).

vite-plugin-domain: no-config ssl domains, powered by @caddy.bsky.social (@vite.dev) Easy as adding `domain()` to `plugins: [...]`. I work on tons of Svelte apps simultaneously, so this is a life saver. npmjs.com/package/vite-plugin-domain

In spirit of "use the platform", is there a reason why svelte-package can't read aliases from vite directly (resolve.alias)? Instead of forcing the user to create kit.alias. For the same reason can't `svelte.config.js` entirely be avoided? I had to add it just to appease svelte-package.

i rewrote a popular next.js site in svelte. LOC before/after: 1/5th* of the code. <3 svelte (this is a follow upon my previous post bsky.app/profile/nuqa...) * 1/5th and not 1/6.7th since there are a few more features to add to svelte version

i rewrote a popular next.js site in svelte. before/after. <3 svelte

minor: `onerror = () => {}` is valid js, but fails in a .svelte.js file. svelte.dev/playground/h...

Svelte: is there a way to attach a reactive object (rune or store) to window? To make the below examples possible - `URL: {window.$route.url}` (if a store) - const url = $derived(window.route.url) - $effect(() => { console.log(window.route.url) }) (I know the idiomatic solution is `context`)

svelte kit docs: > Data will never be preloaded if the user has chosen reduced data usage, meaning navigator.connection.saveData is true. This makes sense, but not for mousedown/touchstart, as that will virtually always result in a click (right?). So this simply slows down svkit sites.

i was reading svelte kit's source. this seems to contradict? or am i missing something.

vite-plugin-domain: no-config ssl domains, powered by @caddy.bsky.social (@vite.dev) npmjs.com/package/vite-plugin-domain

Why is this now a warning? My svelte config is in vite.config.js. [vite-plugin-svelte] no Svelte config found at /path/to/app - using default configuration.

[plugin vite-plugin-svelte:preprocess] Sourcemap is likely to be incorrect: a plugin (vite-plugin-svelte:preprocess) was used to transform files, but didn't generate a sourcemap for the transformation. (x2038) changing `preprocess: {...}` to `preprocess: vitePreprocess({...})` fixes why needed?

MPAs have better back/forward ux due to bfcache. Can kit serialize component state (à la hmr) to catch up? @svelte.dev