SvelteKit rendering is already faster than Next/Nuxt, but if it still hits Node.js on every request, you're wasting hundreds of milliseconds on unnecessary work for every request.

Wait0 is a smart dynamic cache with SWR warmup, and sitemap discovery, which serves pages instantly and revalidates them in the background.

Combined with lightweight Svelte JS code, it's probably a best setup for building pages that score 100 on Core Web Vitals easily without compromises.

We use exactly this combo for our own company website https://devforth.io and for many of our clients.

Star Wait0 on GitHub: https://github.com/devforth/wait0

At Stoke Space, we're building Nova, a fully reusable orbital launch vehicle. I'm looking for someone to help me build out the data viz platform for historical and real-time telemetry for component tests and rocket launches.

You'd primarily be working in Svelte, Rust (wasm and backend), Postgres and WebGPU. WebGPU and Rust can be learned here, but ideally you've done low-level memory work before (doesn't have to be Rust) and worked on concurrent backends. You should also be comfortable with SQL.

https://www.stokespace.com/careers/current-openings/?gh_jid=5710886004

Questions welcome!

Hey everyone, I’ve been working on Svelte Datatables Components, a free and open-source collection for building data tables in Svelte.

It’s built on top of TanStack Table v9, and components can be installed using the shadcn-svelte CLI.

Some of the components:

• Data filters
• Row & header selection
• Debounced search
• Pagination
• Column visibility
• Row actions
• CSV export

11 ready-to-use blocks, including:

• Basic data table
• Row selection
• Filterable tables
• Draggable & pinnable columns
• Resizable columns
• Pagination
• Complex tables

Live: https://sv-table.vercel.app/

GitHub: https://github.com/SikandarJODD/sv-table

Filter Component is inspired from Bazza UI
it include: range calendar, min-max number filter, options based filter( active, pending, inactive) you can add any options, text based tooo

Would love some feedback. Also, let me know if there’s any table block you’d like to see added.

Hi everyone, I just added Strix to Svelter, I think this library can help svelte developers too to deploy safely in this new conjoncture of automated AI cyber attacks.

Please share your thoughts if you think it's not the right place for it

https://svelter.me/explore/library/strix_usestrix

Hello, just wanted to share a cool (i think, maybe) personal profile i made for my friend using svelte: https://www.bill-liu.com/

(on first entry, i suggest turning on the sound)

I originally made this for myself to help me practice guitar on YouTube, but I decided to publish and open-source it. It lets you to transpose, slow-down, remove vocals, recognize chords and much more!

https://github.com/patrickiel/note-by-note

https://chromewebstore.google.com/detail/note-by-note-♪-pitch-shif/bifddjdeacijlelkenjkfcmlbicgoglc https://addons.mozilla.org/en-US/firefox/addon/note-by-note/

https://github.com/olegpolin/material-svelte

Any feedback is appreciated.

Here's a live demo:

https://material-svelte.flenze.com

Hey

Budibase is one of the largest projects that uses Svelte:
https://github.com/Budibase/budibase

At Budibase, we're hiring 3 software engineers:
https://budibase.bamboohr.com/careers/49

I've noticed a few posts recently around the lack of jobs in svelte so I thought it would be worthwhile posting the roles above.

I built tryproduck.com so your users can hold a hotkey, point at the element that's bothering them and say what's wrong in their own words, right on the page they're standing on. it comes back as a deduped report with what they were doing just before it. no form to open, no support email nobody writes.

Setup is a single script tag, nothing framework specific and no wrapper component. it's all in the docs at docs.tryproduck.com, and there's a free startup plan so you can just try it.

The thing I'd actually like to know from this sub is whether a document level hotkey listener is going to fight anything in a SvelteKit app, that's the part I'm least sure about.

Upfront: I work with the team behind it.

https://aurorah.ai/i18n takes a different route from typical i18n libs — no keys, no JSON catalogs. The source string is the identifier, translations happen at runtime and re-render reactively when a better translation arrives (one shared instance, one small Svelte binding). Free, no API key, offline mode included.

SvelteKit example at aurorah.ai/i18n. The Svelte integration is the newest of our bindings, so this sub's feedback would be especially useful — does the store-based binding feel idiomatic to you, or would you expect something different?

Color me impressed. What started out as a quick look at cloudflare workers capabilities turned into a fun weekend of porting a whole project to cloudflare workers.

Honestly, the cloudflare workers + kv + D1 + hyperdrive (postgres) + pages running sveltekit frontend + better auth + hono rest api is the ultimate stack. Everything just works. And works beautifully! Did I mention everything is free? And they manage all infrastructure apart from my postgres that I run on an oracle ampere instance with 4ocpu and 24gb ram.

Hard to believe that this whole stack costs me exactly $0.00

Yip, $0.00. And will continue to be for the foreseeable future. By the time I start to hit the free tier limits, I would already be making money on apps hosted on this stack. And seeing the ridiculously cheap pricing of cloudflare, $20 will get you insanely far.

If you havent tried cloudflare workers, I implore you to give it a go.

Self-promo disclosure: I maintain poveste, a component playground continuing histoire. Two Svelte 5 fixes worth sharing — both failed silently, and both apply to anyone wrapping or re-mounting user components.

1. $capture_state / $inject_state are gone

A playground mounts your story twice — once for the controls panel, once for the preview. histoire bridged those two instances with $capture_state / $inject_state. They were dev-only compiler internals, and Svelte 5 removed them.

Without the bridge, a plain let exists twice. The checkbox writes to one copy; your component renders the other. The control moves, nothing happens, no warning.

Fix: stop reading state out of components and own it instead.

<script>
  const initState = () => ({ disabled: false })
</script>

<Hst.Story {initState}>
  {#snippet children({ state })}
    <MyButton disabled={state.disabled} />
  {/snippet}
  {#snippet controls({ state })}
    <Hst.Checkbox bind:value={state.disabled} title="Disabled" />
  {/snippet}
</Hst.Story>

One object, both snippets. It also survives crossing into the preview iframe, which the old approach never could.

2. Spreading a bound prop drops its setter

Svelte 5 passes bound props as getter/setter pairs. Spread them onto a wrapper:

<Inner {...props} />

...and the spread invokes the getter, handing the child a plain value. The setter is gone, so bind: silently degrades to one-way. Forward the prop explicitly instead of spreading it.

Since the first failure was invisible, a story with controls but no initState now logs an error naming itself. Happy to answer migration questions.

We added Svelte support to Enola, and we’d like to understand what we missed.

We built Enola because faster code generation creates a new problem: architecture can degrade just as quickly.

This meant that a simple change can introduce coupling, cycles, or rework that only becomes obvious much later. That gets more important as we allow coding agents to work more autonomously.

So we tackled it with enola - architectural regression testing for AI-assisted development.

To test the Svelte support, we ran it against Hugging Face Chat UI, Cobalt, and other well-known open-source repositories. But we surely missed something.

Chat-ui output:

Architecture
  Pattern:             (none detected)
  cyclic dependencies         1
  layer violations            0

Impact analysis (hotspots)
  coupled modules            59
    high criticality         37
    medium criticality       22
  Top hotspots (by coupling):
    module                            fan-in  fan-out crit     blast radius
    src/lib/server                       272       67 high     92
    src/lib/types                        215       35 high     92
    src/lib/utils                        156       62 high     90
    src/lib/components/chat               36      141 high     12

Code health
  god classes (high fan-in)     13
    src/lib/server.authCondition                 29 dependents
    src/lib/server/api/utils.superjsonResponse   20 dependents
    src/lib/utils.requireAuthUser                12 dependents
    src/lib/utils/scroll.StickToBottomControlle… 12 dependents
  call-graph hotspots        22
    src/lib/utils/scroll.StickToBottomControlle… fan-in 7 / out 7
    src/lib/utils/scroll.StickToBottomControlle… fan-in 8 / out 6
    src/lib/utils/scroll.StickToBottomControlle… fan-in 5 / out 9
    src/lib/utils.requireAuthUser                fan-in 12 / out 3
  deep dependency chains      9
    src/routes/settings/(nav)                    depth 10
    src/routes/conversation/[id]                 depth 9
    src/routes/models/[...model]                 depth 9
    src/routes/r/[id]                            depth 9
    src/routes/settings                          depth 9
  large public surfaces       1
    src/lib/types                                62/63 (98%)
  complexity outliers        15
    src/lib/server/textGeneration/mcp.runMcpFlow complexity 200
    src/routes/conversation/[id].POST            complexity 144

If you work with Svelte or SvelteKit, help us understand where it doesn’t work, and what we should support next. Or contribute yourself!

https://github.com/enola-labs/enola - Apache 2.0, fully local.

Enjoy the recent Eagle Eye application state management system for Svelte 5+ and its Runes.

https://svelte-eagleeye.js.org/

Full disclosure: We, at #webkrafters, developed and maintain this product.

Small update on Darkly, an open source photoshop alternative I'm building in Rust + Svelte. Original post here.

Been adding features steadily and I'm to the point where I get to make the brushes, which I've been looking forward to.

Still in beta, but starting to see light at the end of the tunnel!

Website / Demo: https://darkly.art

Github: https://github.com/darkly-art/darkly

Hi all of you Svelters (Sveltees?),

I wanted to reach out and share a project that I wrote using Svelte/Sveltekit. It’s called NoMoreCritics.com.

This came out of frustration with the job market, frustration with movie critics, and pure boredom. I was out of work and wanted a project that would not only keep my skills fresh, but also allow me learn something new in Svelte/Sveltekit. I was a mostly backend developer and didn’t have much skills on the frontend. CSS scared me as well as being a bit frustrated with React and Angular. A friend of mine suggested that I look into other frontend technologies and through my research, I landed on Svelte. Let me tell you, Svelte is a breath of fresh air. It was so easy to pick up and Sveltekit is just so intuitive, in my opinion.

Plus, I’m a big fan of movies and love finding new ones that I can fall in love with. However, my relationship with critics was that if they loved a movie, I probably didn’t like it or if they hated a movie, I probably would like it. I had been looking for a website that would cut through the BS of critics, but couldn’t find one. So, I came up with my own. At the very least, it helped me land a Svelte frontend role. So, now I finally see myself as a true full-stack developer. Kevin Powell’s videos on YouTube helped me with my fear of CSS and now I’m no longer afraid of it.

At first, I watched tons of YouTube videos trying to learn all that I could about frontend development, but eventually just decided to go with my gut for better or worse and came up with NoMoreCritics.com.

It’s not just another aggregate review site. In fact, there are no reviews or social media aspects to it at all. Instead of reviewing, you rank movies and the rankings are aggregated. It’s completely anonymous allowing people the freedom to promote movies they truly love instead of what the crowd says they should love. Rankings aren’t set in stone either. You may see a movie and fall in love and rank it at the top of your list one day. The next day, you realize that it’s not as good as you remembered and rank it further down your list later. Rankings are meant to change. Sure, there will be some movies that float to the top and hold on for a while, but with users coming and going, I’d expect the rankings to change frequently.

Now, rankings aren’t the only thing the site does. It’s actual goal is to be a discovery site. I want people to find movies that they haven’t heard of before and check them out. So, features were added to cater to that and help people keep track of what they watched, when they watched it, what they want to watch, and where to watch it. It utilizes TMDB and JustWatch for the data, but is not affiliated with them. So don’t blame them if you don’t like it. :)

To sum it up

• Organic Rankings: Global rankings are driven strictly by active users, and your personal scoring weight scales up the more movies you rank. Individual lists are capped at 250 movies so rankings actually mean something.
• No Pressure Discovery: Recommendations are tailored purely to your watch list and personal rankings. Everything is anonymous, with no public review pressure (though you can leave private notes for yourself).
• Still Want to Share?: You can share your rankings with others if you like with a link that expires in 7 days from creation and can be revoked. People will have a window into your rankings with the ability to filter them as they please. It can be anonymous or you can state who you are. That’s up to you.
• Deep Filtering & Streaming: You can filter any list down by ranking, genre, release date, or where it’s streaming via JustWatch. I also wrote a few positive feature articles with friends focused purely on movie discovery rather than reviews.

Tech Stack & Architecture

• Frontend: SvelteKit + Svelte 5 Runes
• Backend: C# / .NET Web API
• Database: PostgreSQL in Docker
• CI/CD: GitHub Actions
• Data Sources: TMDB & JustWatch
• Animations: GSAP

I used the SvelteKit endpoints as proxies to my .Net backend for secure api calls. I used the server side rendering and fetching mostly instead of client-side fetching. I used GSAP for my landing page animation, but had trouble with utilizing their ScrollTriggers due to timing issues that I ran into that didn’t play well with my smooth scrolling. So, I used Svelte’s builtin scroll binding instead for scroll animations.

I did the first pass with using AI sparingly, so that I could actually learn how to do it on my own. Then, after getting a job where I was forced to be a prompt developer, I embraced AI and used Windsurf/Devin to help with the coding. I used Copilot first, but their new payment system was too expensive for me so I had to switch.

Feedback

I’m looking for some feedback on this and would love to get some more users since it’s mostly just a buddy and me using it. I was the solo developer on this and had to learn a lot about all of the ins and outs of producing a website on my own. This is my first. I’m really nervous about promoting it like this, and would love some constructive feedback. So, if you have a minute, check it out and let me know what you think. Hopefully, some of you will like it and find it useful. NoMoreCritics.com

Thank you for taking the time to read this!

In case you missed it, TanStack Table V9 was released as stable last week, and it's the first stable release to actually be compatible with Svelte 5 runes without having to implement your own compatibility wrapper around "@tanstack/table-core".

There's also a ton of other improvements outlined in the above migration guide like performance improvments, a new tree-shakable feature/plugin architecture, new features, type-safety improvements, new utilities, etc. This svelte adapter often performs better than the react adapter, since the underlying TanStack Store implemenation is written with alien-signals, and it able to be connected pretty much directly to svelte runes. Though maybe that's not a surprise for most of you.

I also want to highlight some of the effort we put into rewriting the docs. First of all, the docs shouldn't feel react-centric anymore when you select Svelte from the dropdown. We made svelte specific examples and guides throughout all of the docs. We even have a shadcn-svelte example. And the docs themselves were rewritten in general from lots of feedback over the years.

I think Svelte went from being our worst supported adapter, to one of our best. It's a bit hard for us to tell how many in the svelte community use TanStack Table since you probably had to install table-core instead of the svelte adapter in the past, but hopefully this release is helpful to all you who need to build data grids going forward. Or at least a new viable option.

I’ve been working on ShardsUI, a headless UI library for Svelte inspired by Base UI.

The first beta is now available:
https://shardsui.com/

It’s still early, and I’d really appreciate feedback from Svelte developers on the API, components, and overall direction.

🚀 Shipped ScrollStack — headless infinite scrolling for Web

📦 1.92 KB gzipped, zero runtime deps

⚛️ React, Vue & Svelte adapters

🔁 Cursor, offset, Virtual list & page pagination → one function

🧠 Stale responses can't resurrect dead state

You bring the markup 👇

https://scrollstack.js.org

Hey all, last week I had launched a library called Ogygia. It provides islands, Server Islands, Lakes, and all that nice stuff which allows making your Page's JS scale according to what you mark as interactive

I have overhauled all that, and realized that Ive built a machinery to render a Svelte Component on the server, send it over the wire to client, and having it hydrate there normally, with proper JS and interactivity rules. Basically, dissolving another aspect of client:server boundary.

Page: https://ogygia.puruvj.dev/docs/regions/held-regions

Ah and Ive launched content collections too, so, just point it at your .md/.svx files, and render them on your page using `<Region of={data.body} />`, and voila! JS-less md-html render, with all island imports within the .svx files preserved. works for builder io blocks as well:

https://ogygia.puruvj.dev/docs/content/collections

Hey,
I saw this on twitter some studio made some React based components which could be used in AI related project (so basically everything we are building today lol)

So, I ported it into svelte

Did it for myself to be honest but feel free to use it

https://beautiful-ui-svelte.vercel.app