I just finished looking at the 2026 Developer Survey but something doesn’t add up for me.

Svelte is at 8% usage and SvelteKit at 6%. Admired is strong (59% and 64%), and Svelte is at 10% desired. It was highly desired last year too but that didn’t turn into more usage this year. Meanwhile Node.js (46%), React (42%) and Next.js (21%) dominate as usual.

Do the desired and admired numbers even mean anything? Admired only counts people who already use it, and desired is easy to say but hard to act on when jobs and existing codebases decide what you actually write.

Also the official Svelte jobs site closed this year link. By itself maybe not a big deal, but alongside flat usage it must be a tough time to rely on Svelte for work.

Dare I say it: is Svelte dead?

I love using svelte but maybe it’s just a well-loved tool that stays niche, like Phoenix or Axum.

What do you think?

Hey folks, been working on Bref-ui, a Svelte-first, human-first, agent-first UI library. Started building it for stuff I needed, and it's already running in five of my projects!

I've used Tailwind a ton at work with Next.js and it's amazing tbh... but for me tho, it still felt like learning another thing, I'd rather write CSS directly. Which, Svelte makes pretty easy.
That said, I get that it's not everyone's thing. Some just wanna build without fussing over CSS, so I think I've made something for you folks too.

I love shadcn's source ownership approach too. But in my projects, the dependency stack felt like a gazillion more things to keep track of. With how fast stuff moves in the React ecosystem, that was more mental overhead than I wanted. I've always loved Svelte's batteries included feel, so that inspired Bref too.

And sometimes I want the source so I can mess with everything, sometimes I just wanna import a button and get on with my day lol. Bref lets you do either.

Now I'm going down the rabbit hole with marketing components, automatic site generation, generative UI and tooling to help agents discover, compose, customize and verify interfaces. Big undertaking, lots still cooking, but it's fun as hell.

I'm pretty bullish on agents, but I still wanna understand and control the code that ships. I review every change I make with them. I'm the maintainer, it's my responsibility, and code review stays part of the deal. I hate slop as much as the next dev.

Using it in my own projects keeps me honest too. If something's annoying to customize or breaks, I get to deal with that shit firsthand.

Would love feedback on the components and where this is headed. Anything feel awkward? Anything you'd actually wanna use?

Praying the Reddit lords are nice this time ahah
https://github.com/feuersteiner/bref-ui

Xivly is an open-source reader for research papers (video above).

One SvelteKit codebase, three targets.
The same app ships as a Tauri desktop app, a static site on GitHub Pages, and a Chrome extension. Platform differences sit behind a small adapter: Rust file access on desktop, the File System Access API (or OPFS) on the web. The extension build switches SvelteKit to the hash router, since an extension has no fallback page for /read, and moves the inline bootstrap script into a file, since extension pages can't run inline scripts.

svelte-pdf-mini.
As the reader grew, I pulled the PDF logic out into a reusable library, in the spirit of bits-ui / melt-ui: headless, composable parts (Document.Root, Viewer.Root, Viewer.Pages…), each taking class, style, a bindable ref and a child snippet. State lives in plain runes classes on top of a framework-free core. It covers virtualised rendering, zoom, find, annotations that round-trip as standard PDF annotations (they open in Preview and Acrobat), and research-paper extras: citations with hover cards, figures, tables and cross-references.

```svelte
<Document.Root src="https://arxiv.org/pdf/1706.03762">
<Viewer.Root zoomMode="page-width">
<Viewer.Viewport><Viewer.Pages /></Viewer.Viewport>
</Viewer.Root>
</Document.Root>
```

Xivly: https://github.com/julien-blanchon/xivly
svelte-pdf-mini: https://github.com/julien-blanchon/svelte-pdf-mini (docs: https://julien-blanchon.github.io/svelte-pdf-mini)

It’s a habit by now to just create a new svelte project no matter what I’m building. And so far it was never anyhow in the way. Nothing but a smooth experience.

This specifically is a demo of a game I’m working on. I was playing with some flocking algorithms and thought “this is so freaking satisfying”.

Curious what you think, if you give it a try!

Link: https://nohope.io

• Home page: dithr.github.io
• Web version: dithr.github.io/app
• Android app + source code (MIT License): github.com/redphx/dithr

I bought several NFC-powered eink displays (from Good Display, Waveshare, Xteink, EZ Sign...). I didn't like that I had to install different apps for different displays (and I don't trust them), so I decided to make my own.

You can use this to prepare images for other displays from TRMNL, Seeed Studio, Xteink... too.

Some features:

- Privacy first: No trackers. No ads. No uploads. No servers. All on-device.

- Open source

- Mobile-optimized UI: the UI is designed with mobile users in mind.

- Multiple dithering methods: supports error diffusion, ordered dithering, halftone patterns...

- Simple yet powerful canvas editor: supports layers, images, texts, shapes...

- Direct hardware sync: sync dithered image directly to supported devices, including Waveshare, Good Display, and EZ Sign displays.

AI usage disclosure

This is not a vibe-coded project. I used Claude (free tier) to assist me with creating shaders and the history + layers manager. Other than that I code it myself (took me 3 months but I learnt a lot from it).

I hope you'll find it useful.

Thank you.

Hey everyone! I’ve been building Sveltewind, a Svelte 5 component library styled with Tailwind CSS 4 and compatible with SvelteKit.

The part I want to highlight is how theming and styling work across components:

• Global/shared themes: keep styling consistent across your app through a shared theme.
• Included or custom themes: start with the themes provided by the library, customize them, or create your own.
• The themes ( provided or your own ) are simple javascript files.
• Share styles between components: reuse styling from another component instead of defining the same styles separately for each one.

That last point is a big part of the approach. Themes give you a common foundation, and sharing component styles lets you carry those styling decisions into other components. You can start with the provided appearance and build your own visual style on top of it.

The docs and examples are now live:
https://sveltewind.com

GitHub: https://github.com/sveltewind/sveltewind
npm: https://www.npmjs.com/package/sveltewind

I’d appreciate feedback, especially on the theming and cross-component styling approach. How do you currently handle shared styles across components in your Svelte projects?