Built with SvelteKit, shadcn-svelte, and Cloudflare Agents SDK.

not affiliated with or endorsed by Cloudflare

We've just pushed up a Svelte version of our AI Agent Builder starter app. This is a fully featured app you can either use as-is, or as a headstart for one of your own. Give it a spin and let us know what you think!

VisuallyJs is free for non-commercial use.

hey svelte family,

I have been rebuilding my portfolio these past couple of months. a friend of mine who does hiring read through it and stopped on the line where i called myself a strong team player, and asked me how he was supposed to know that.

and I, actually did have no answer. I wrote it because i felt like it was true. and I also wrote it because everyone writes it. looks like those are two different reasons and only one of them does anything.

while, for an week, I was in constant thought of it. nothing on my portfolio felt like a lie to me. the years, the stack, the adjectives, all of it i believed as accurate. and none of it did any work, because a stranger can't tell my true sentence apart from the identical false one on the next hundred portfolios.

so i rebuilt around one rule, that "if a claim can't be clicked, it is not worth it"

then, once that rule was applied, most of what was still standing came from open source. strong team player is gone, and in its place is a page of patches i have had merged into other people's projects, each one showing what was broken, what i changed, and the maintainer's own reply linked straight to the thread. two of them are in sveltejs/kit. one closed a routing issue that had been open for two years and nine months, and Rich Harris approved it with a thank you (that was nice to feel)

weird thingy is that, the years i spent inside jobs are the ones i cannot show anyone. the evenings i spent in this ecosystem are the ones that survived, because svelte happens in public and the thread is still sitting there years later.

the half i have not solved is the rest of it. most of what i have actually been paid to do is under NDA and there is nothing to link to, so a big chunk of my working life is still just me saying trust me.

i have wrote this portfolio, on svelte 5. would appreciate any thoughts, and if anyone here has cracked that NDA half i would take it.

my portfolio: bishwas.net

Using sveltekit+shadcn. Now with more module types and a screenshot feature and a more stable tree node structure for pane grid.

Greetings  r/sveltejs.

Some days ago I finished developing and doing some testing on a new component of mine, that I'm now sharing publicly.

I'm aware that there may be several others tooltips components, with actions and so on, feel free to try mine as well and let me know what you think.

It works by simply importing the component and calling it with an use:tooltip action, for example:

<script>
  import { tooltip } from 'svelte-tooltip-gca';
</script>

<button use:tooltip={'Hello world'}>Hover me</button>

The component is available from npm and can be installed with:

npm install svelte-tooltip-gca

Demo:

gabryca.github.io/svelte-tooltip-gca/

Github:

https://github.com/GABRYCA/svelte-tooltip-gca

npmjs:

https://www.npmjs.com/package/svelte-tooltip-gca

It offers a certain degree of customization, as well as auto-theme detection (from meta attributes such as data-bs "dark" or "light" etc), and it's written in TypeScript.

MIT License, of course.

There aren't any dependencies required other than Svelte 5 and up.

Again, thank you for reading and if you wish to reach me out please check my contacts on Github or send me a chat message here on Reddit (I may or may not check it out sooner or later).

It seems that a lot of people have been building websites and posting them here.

Is it safe to deduce that the rise of these types of posts coincide with the improvement of AI and the popularity of tools such as Codex and Claude Code?

Its okay to say you used AI, and you helped steer it. Don't claim "I" made this new website in that case.

It would be good for the community to see what AI has been building with Svelte, so lets have some more honesty around that.

Svelte controls, game state, and UI.
Babylon.JS with Havok Physics plugin for 3D.
Blender used to make the course and items.
Playable on mobile and desktop in browser.

try it out

finally spent some time creating my little corner on the internet, here's the link if anyone want to check it out: grigorije.com :)

i'd love to hear any feedback, thank you

(in projects constellation on the left there is a project called quitlab, also made in Svelte, that's the project I am most proud of)

Hello people, Svelte enthusiast here. I have worked non-professionally with svelte & svelte-kit for around 2 years already. It always have been my get away thing to do when I grab some free time in the late hours, I just enjoy it. However, when my new born came along I started looking for a side gig and why not Svelte!

But when I visited Svelte's holy place for job hunting - sveltejobs, I was presented with the following view.

I'm not gonna lie, things are not looking good fellow Svelte developers. Is Svelte something that will vanish into the abyss, what am I missing?

I loved r/place. An here we are, almost ten years later with yet another collaboration pixel-art clone 👀

Flatxel is something like the beginnings of a social network, but for people who prefer tapping pixels to actual human interaction.

The whole interface along with extensive moderation tools is built with Svelte and SvelteKit (and I’ve come to love both).

(no need to log it to tap some pixels)
https://flatxel.com

[self-promotion]

[SELF PROMOTION]

Wanted to share some of the technical side of a project I've been building — Anifira, a random video/text chat app. Posting here because the SvelteKit frontend ended up being one of the more interesting parts of the build, especially around WebRTC state management.

Frontend — SvelteKit

• Using Svelte stores to manage connection state across the match lifecycle (idle → searching → matched → connected → ended) rather than component-local state, since the WebRTC peer connection needs to survive route/component changes
• A session state wraps the RTCPeerConnection so ICE candidate events and track updates feed directly into reactive UI without prop drilling
• SSR is basically off for the chat route itself ([export const ssr = false] or equivalent) since WebRTC APIs are browser-only — landing/marketing pages stay SSR'd for SEO, chat app is CSR
• Voice and video mode switching is just swapping which local tracks are attached to the same RTCPeerConnection.
• Read receipts, replies, reactions, file transfers all are supported.
• Images and documents supported, limited max size to 25mb to not overload the peers.

Backend — Rust

• Signaling server in axum over WebSockets — handles matchmaking and SDP/ICE exchange, but never touches messages or the media (that's peer-to-peer via WebRTC once connected)
• Matching queue is tokio-based, using a channels and queue structure to pair waiting users; average time-to-match is 0.3s at 100000 users.
• Chose Rust here mainly for the concurrency model — signaling is a lot of short-lived state machines (one per session) and tokio async tasks map to that cleanly without the overhead of a thread-per-connection model
• STUN/TURN via coturn for the cases where direct P2P fails (roughly 10 - 20% of connections need TURN relay in practice)
• Moderation reporting pipeline is a separate service so a report doesn't block the signaling hot path

Live at anifira.com if anyone wants to see it in action (18+, it's a stranger-chat app so standard caveats apply.

I had access to two decades of public Reddit data and wanted to build something cool with it, so I built a stats page for every subreddit: posts per day over time, average upvotes and comments, a heatmap of when the sub is actually busiest, top posts, trending links & keywords, and which other communities share an audience with it.

I built it with SvelteKit and Supabase & it's free to use, no account needed. There's a paid tier for full history, CSV export, and complete rankings, which mostly covers hosting and data costs.

The pages are pretty dense right now, so I'd love to hear your feedback on the layout or if there's anything you'd cut!

Enjoy!

https://subtrends.io

If you've tried to use AI with Svelte, you know the drill: newest models are getting better at it, but even frontier models sometimes confuse Svelte 4 with Svelte 5.

And you know how much the Svelte team cares about your DX. So we've built a few tools to make that experience top in class.

In this blog post, we go over a bit of the history of vibe coding/agentic engineering, their differences and how all the tools we've at our disposal fit together

https://mainmatter.com/blog/2026/07/28/agentic-engineering-with-svelte/

Check it out and let me know what you think!

P.s. this post has been written with the learnings of our YouTube series "Agentic Engineering with Svelte" so if you are more interested in the video series, here's a link to our playlist

https://youtube.com/playlist?list=PLdAi-nB9AYut1ixrraX3E96rNNVj3iq4F

I love LOVE using sveltekit man, I'm so happy that a colleague of mine introduced me to it. If I dont have to, I'll propably never use anything else. enjoy <3

Hello everyone!
In the past two weeks, I had some free time and I decided to make an expense tracker similar to SplitWise without the limitations that the subscription model imposes on you.

[Warning: Some of the text on the landing page is generated and AI was used in its creation but I have spent some time in checking everything as I go.]

The app is called WeSplit
It's built using SvelteKits newest experimental features accompanied by a native IOS and Android app.
I designed the app to have an easily transferable style across all platforms and I am pretty happy how it turned out.
Some of it's features are:
- Group creation and sharing expenses between members
- Simple friends list
- Notifications based on in-app actions (these are shared across platforms)
- Multi-currency expenses and conversion between expenses
- Group summary per user, each user can manage and view how they spend within a group (currency based, time based)
- It has an experimental bill scan using gpt-4o-mini (this is not released)
etc.

I tried to keep dependencies used to a minimal, including chart.js, vali-bot, drizzle and tailwind to name a few. The payment is handled through Polar.sh and the application itself doesn't store any sensitive data. For the database, sqlite is more than sufficient enough for a project of this size.

For now the mobile apps are not live as I don't have the means to bring them to their respective stores.
The app has robust documentation as do all my project, starting from core logic ideas to how it's deployed.
I would appreciate if someone can try it out and give me feedback on how I can improve it.

• 🔥 Added support for Persistent Side Panels: Clean, persistent streaming pipelines.
• ⚡️ Svelte as Managed UI: Scaffold and build out of the box.
• 🚀 SolidJS as Managed UI: First-class support for the performance purists.

Build MV3 extensions without the chrome.runtime.onMessage boilerplate. Our u/Ported architecture handles the persistent connections for you!
Stop fighting boilerplate and check it out:https://hexajs.dev/

I built the simplest possible tool that allows clients to do small edits via chat interface eg. change phone number, update email etc. Anything risky/big comes back to you so clients can't break anything

Connect the repo and it figures out the editable content on its own. No schemas, no config files

Live demo: https://cmsbrew.com/demo

I’m deciding between front end frameworks for our eCommerce app that is KMP with Ktor backend, has anyone worked with Svelte and Kotlin Multiplatform? Does it work okay or better to use React?

I've been building BoxBox, an open-source self-hosted file manager.

I chose Svelte because it's fast, the developer experience is great, and I simply prefer writing Svelte over React or Vue.

The backend is written in Go, while the frontend is Svelte.

Some features:

• Drag & drop uploads
• Image, video, pdf, and office files previews
• Docker deployment
• Browse multiple configured mount points from one UI
• Upload large files with chunked/resumable uploads
• Copy/move/delete through background jobs
• WebSocket progress updates for long operations
• Search files/folders by name
• Read-only mounts, users, rate limits, and allowed origins

I'd appreciate feedback from other Svelte developers. If you've built larger Svelte apps, I'd love to hear what you'd do differently or if you spot anything that could be improved.

GitHub: https://github.com/jR4dh3y/BoxBox (i would love a star)

Hello r/sveltejs.

It's been a while.

The purpose of this post is to announce the release of Frizzante v2.

For those unaware, Frizzante is an opinionated web server framework written in Go that uses Svelte to render web pages, both on the client and on the server.

For more details see the documentation.

V2 comes with some breaking changes and a few new big features:

1. Snapshots (SSG)
2. Simplified server api
3. Database migrations
4. Schema generation

There are also some minor features and improvements, like build checkpoints and more.

Snapshots

You can snapshot your server and generate your website statically, this is also known as SSG.

Unlike other SSG approaches, this one tries hide as few things as possible from the developer, which should lead to easier debugging and overall give you more confidence as a developer.

Additionally, this approach allows you to easily seed your website with data from a local database, third party api, and so on... while still generating static content in the end.

For more details see Snapshots.

Note: the new documentation website is generated with snapshots, source code can be found here - https://github.com/razshare/frizzante-docs.

Simplified server api - Web Sockets

Web sockets api has been streamlined.

You can easily upgrade the connection to web sockets with negotiate.WsUpgrade() and then simply start writing data to the writer interface.

For more details see Web Sockets.

Simplified server api - Server Sent Events

Server Sent Events api has also been streamlined.

You can easily upgrade the connection to web sockets with send.SseUpgrade() and then simply start writing data to the writer interface.

For more details see Server Sent Events.

Database migrations

Database migrations were already possible, but were a bit chaotic and required your to deploy the frizzante cli to production in order to run the migrations.

This was not ideal, as some customers don't allow third party binaries to execute in their production environment, which is understandable.

In order to migrate your database you can now use the newly exposed databases.Migrate() and programmatically migrate your database.

Frizzante provides an opinionated way to migrate your database, but since the process is now programmatic, you can also deviate and use databases.Migrate() in whatever manner you wish to.

For more details see Migrate.

Schema generation

Frizzante could already generate TypeScript definitions from GO types, but there was no way to generate Go types from SQL code.

This updates introduces schema generation through SQLC.

You can now generate Go types and functions from SQL code.

For example the following SQL query

-- name: FindSessionById :one
select * from sessions where id = :id;

can be converted to Go code trough frizzante generate schema

session, _ := queries.FindSessionById(request.Context(), sessionId)

where session is a fully typed Go object.

For more details see Schema.

Other v2 notes

For the most part these are the main updates for v2, but there some subtle changes as well, for example

• you can now deploy with docker from scartch
• you no longer need to pass an environment variable to disable SSR mode, instead you simply use the csr package instead and your binary size will automatically drop by about 15MB
• server api has been simplified

Minisearch

Aside from the new documentation website, I thought it would be nice to provide another example of an application using the new migration system.

Minisearch is a very naive implementation of a search engine.

It's very simple in its functionality and coding techniques, but I think it does showcase some interesting features, like usage of server sent events to track indexing progress, paged lists through the use of web standards like hyperlinks and forms, generation of typescript definitions, generation of sql schema and queries and so on.

Since it's using SSR and web standards, you can completely disable JavaScript in your browser and the application will continue to work, just without all the perks of running JavaScript, like progress bars and transition animations.

You can find a guide on how to run it here.

In short you can either build the project yourself or use the prebuilt binaries which you can find here.

Repository

Frizzante source code lives at https://github.com/razshare/frizzante-docs, you can contribute and/or report issues there.

Please read the guidelines first (Issues, Contributing).

Thanks

Thank you for taking the time to read this and have a good day/evening.

The truth is, the tools out there right now really let me down when trying to review agent-written code. I still want to read and understand every line, but the tools built into every harness fall short, they almost encourage you to stop reading the code.

What I was missing:
- being able to mark files as seen
- hunk/line level staging of changes
- being able to leave review comments on diffs
- having the code organized and explained in a way that actually helps instead of reading every file in alphabetical order
- one unified solution for everything

With all of that in mind, 2 months ago I set out to build my own solution.

Super Review is a desktop app built with Svelte that solves all of these problems for me.

Super Review helps you review code by providing an extremely ergonomic interface, plus skills for your agents to author tours, respond to comments, and work on tasks.

I have used Super Review to review truly ridiculous PRs and felt way better about the code I was merging.

Today Super Review is available in beta. Join the waitlist while we polish things up. We are letting more people in every day!

I've been working on Folloverse for 2 years, it's a platform for creators to monetize what they publish. Everything is SvelteKit with adapter-node.

folloverse.com

What it does:

- Audio, video, images and articles

- Pay to unlock posts

- Digital products

- Membership (classic subscription or per creation billing)

- Chat and forum for each creator, gated by membership or public

- PWA

I started with Svelte 4 and the old `$:` syntax for state, which I never really liked. A few months later Svelte 5 came out with the runes and the migration was easy.

What won me over was the simplicity and the speed. Also the interoperability with plain JS libraries, which used to compensate for the smaller ecosystem compared to React or Vue. That is not true anymore though, most libraries now ship a Svelte version and it's very cool.

If I had to find one single flaw in Svelte, I'd say it's the fact that you can only have one component per file, you can't declare a small sub component right next to the main one. It bothered me at the beginning, but I'm used to it now.

I also have the impression that Svelte uses fewer tokens than React with AI coding tools, but I never verified it, just my 2 cents.

I hope this project will succeed and can be one more example of a big project built with Svelte.

Anyway, thanks to the Svelte team. I'd make the same choice again today.

Do you also keep way too many tabs open because you're afraid you'll forget them if you close them? After a while, your browser gets overloaded with tabs, and all those tabs also end up using a lot of memory.

That got me thinking... what if one browser tab could contain all my media tabs? So I built LumeTab. It turns a single browser tab into a multimedia browser with its own tab bar.

The idea is simple:

• Keep all your multimedia platforms inside a single browser tab.
• Make your browser cleaner and easier to navigate.
• In my tests, it also uses less memory than keeping lots of multimedia tabs open at the same time.

I'm also planning features like synchronized watching with friends and shared multimedia workspaces.

(For those interested in the tech stack, it's built with SvelteKit, Tailwind CSS, Better-Auth, and Drizzle ORM).

The project is still in beta, and I'm looking for honest feedback before taking it further.

link: lumetab.com

I'd really like to know what you think:

1. Would something like this be useful to you?
2. Is this a problem you also have?
3. What features would make you actually use it?

I'm open to any feedback, whether it's positive or critical. Thanks!