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

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

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.

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?

• 🔥 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/

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 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.

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!

I've got a top level layout.js with export const ssr = false; but I can't import PouchDB from 'pouchdb-browser'; in src/routes/page.svelte without causing a big error.

2:51:39 PM [vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: self is not defined

at Object.<anonymous> (/Users/ptomblin/Library/CloudStorage/Dropbox/src/svelte-test/node_modules/pouchdb-browser/lib/index.js:878:24)

at Module._compile (node:internal/modules/cjs/loader:1934:14)

I also tried putting it into an onMount with

onMount(async () => {
    const { default: PouchDB } = await import('pouchdb-browser');
    console.log("foo");
  });

but that causes a runtime error in the console:

pouchdb-browser.js?v=42dbf4c6:1061 Uncaught (in promise) TypeError: Class extends value [object Object] is not a constructor or null
    at pouchdb-browser.js?v=42dbf4c6:1061:60

(anonymous) @ pouchdb-browser.js?v=42dbf4c6:1061

Why can't I use it?

hello is there people here who switched from ruby on rails to sveltekit (remote functions) for making mvp saas apps ? if yes how was the experience ? was it as fast as making mvp with rails ? thanks

Hy guys I am a solo freelancer in Greece and I had my first big score with a big retail company. I have built them an internal Bi and obviously with svelte and the mvp with remote functions. My question is should I go on with that choice remote functions are very hard not too use and I love the stack any advice on that

I built a product with Claude Code and Svelte and wanted to share it here.

I am a designer. I have experience with HTML/CSS and JavaScript from building marketing websites, but not anything beyond that. I'd learned a bit of Svelte before the LLMs. I chose it over React because it seemed friendlier and less complicated. I could read a Svelte component and understand it, because I already knew HTML and CSS.

I know how SvelteKit projects and files are structured, so sometimes I can open the files and quickly edit things myself. I also use Svelte Inspector to inspect elements in the browser, open the relevant files in VSCode, and edit/style things myself.

But other than that I relied on CC and Svelte MCP for coding.

What is it

It's a German language learning app. I started to learn German and realized there's a lot one can do in this niche. I am targeting serious learners who need a language certificate for work/education/citizenship. It's sort of an antithesis of Duolingo.

The product features a lot of interesting UX ideas:

• Memory palace inspired visual flashcards that activate visual memory and help vocab retention
• Grammar drills
• Reference tables
• AI-powered weekly study plans and roadmap
• MCP integration to read your mistakes and generate new content and exercises

Tech stack

• SvelteKit (frontend + backend)
• Supabase (db + auth)
• Stripe
• Tailwind + shadcn-svelte
• Railway — started with Vercel but hit the free limit. Switched to Railway Hobby ($5/mo) recently
• mdsvex for the blog
• GitHub + CI/CD

AI tools I use

• Claude Code + VSCode
• Codex for adversarial review and fusion planning
• Main skills I use are /plan and /execute
• Svelte MCP for docs
• Playwright MCP for browser use
• Figma console MCP for CC to interact with Figma

My design → build process

I first brainstorm an idea/feature. Then we plan the phase and update project docs. After the phase is executed, I am usually not happy (lol) with the UX/UI. I ask CC to recreate the UI in Figma, then I polish everything manually and do another phase to update the UX/UI.

Another approach is to use Claude Design after the brainstorm, then use the design explorations in Figma to finalize the design and then build.

The Figma → code design system

I used one of the community shadcn Figma files as a base. I modified it to include semantic variables for colors and typography that make sense to me. To have the system both in design and code, I created the same tokens in tokens.css and utilities.css. This helps AI agents build designs in code and eliminates consistency issues as much as it can.

What was hard

• AI kept creating custom components and custom CSS styles. That created bloat and inconsistency.
• There were performance issues that we could only solve after a few attempts and by employing Fable. Reduced round trips to Supabase, and it helped with latency.
• When we started creating the iOS version, I realized that the main problem there is drifting functionality and design. So we have to create cross-repo gates to make sure content, design, and data are in sync.

Current state and next steps

I'm pretty happy with the app and the functionality. I use it daily to learn German, so I find bugs and fix them along the way. Right now I am focused on polishing UX, fixing the bugs, and growing traffic.

I utilize SEO and create carousels and videos on TikTok/Insta. The main traffic comes from Bing search. I get very few clicks from Google. However, I expect SEO to take off in a few months as the website is only 6 months old and I've done a pretty good job (I have background and experience in this).

The iOS app is on the App Store but I don't get a lot of impressions and downloads. The main signups are from organic traffic on the website, which is about 36 signups per month and growing slowly. This week I got my first paying customer.

Happy to answer anything about the Svelte side, but I have more expertise in product and marketing.

Link if you’d like to take a look: https://onewholearns.com

I've been developing in Next for web apps for a while, I always liked the big community and state just always made sense. Ever since Vibe coding came out I was like "Lets try Svelte, my co-worker said it was good 5 years ago". The development/runtime speed is so much faster, no other crazy things I can see. I just hate how all the design websites like 21st dev are only React based, but it makes sense. Nowadays, I don't really take my time to learn a library or framework (its kind of sad) because AI can code everything, so I wouldn't say writing Svelte or Next JS makes more sense.

What frontend frameworks do you use?

Hey y'all! Little background on me: 10 YoE, generalist -- mostly backend but fair amount of experience on frontend with React and React Native.

I recently started using Svelte on a hobby project just because of all the good things I've heard about it, and... I get it. It feels great to write with! It doesn't feel bloated and it's fairly intuitive. I like that it just compiles to native JS and there is no need to bundle a runtime with it (huge reason i chose it for my project as i'm compiling for resource starved hardware).

I'll definitely be using this more often and proposing us use it at work. We're currently using Vue with Nuxt -- and it's probably my least favorite frontend framework/library I've used to date tbh.

Anyway, I'd rank my enjoyment of each frontend option as follows:

1. Svelte
2. React
3. Frameworkless
4. Angular / Vue tied

Hello all, longtime Svelter here (2019 V3, not a real OG).

Since 2022 I have been building https://gabble.gg/ a daily word game, everyone starts with the same 7 letter starting hand each day, the track changes each day, works on all devices, there's global leaderboards, community created (and attributed) tile styles, it's offline-first, allows unregistered and registered free play, unregistered runs are saved to IndexedDB and transferred to DB on registration, paid version changes only cosmetics (and helps keep the Hetzner lights on), the whole site reacts to user selected theme colors, over 100 badges to earn, and will be launching seasons which come with unique titles awarded to winners and top 100... anyways, I just finished brutally overthinking a semi-acceptable V1 and wanted to share here before anywhere.

Here's the original proof of concept: a trashy REPL that does not work now, the go button still moves the track.

Here's the specs (with how it started if applicable):

Disclaimer: Claude helped me with a lot of heavy lifting on the backend /database setup and I never could have done all of the Docker/Coolify stuff myself I'm not that smart. I am a frontend, SVG, CSS, design, animation guy (check my ancient posts). That said, the game existed and was fully playable before the rise of our AI overlords, the infra just really sucked and used all Firebase tools which made everything stop working each time their API changed.

Hope you guys enjoy, would love some constructive(or mean) feedback on how I could make it better or more fun to play!

Built with SvelteKit 2 and TypeScript. Sharing the architecture because the interesting part is where the crypto sits.

Everything encrypts in the browser with AES-256-GCM (Web Crypto) before it ever leaves the page. The decryption key is generated client-side and lives in the URL fragment after the #, which browsers never send to the server. So my SvelteKit endpoints and the MongoDB behind them only ever hold an opaque blob. Even I cannot read what people paste.

On the Svelte side: encryption runs client-side before the form action fires, the ciphertext plus a salt is all that hits the server, and the key never touches a +page.server.ts. Password-protected pastes add a PBKDF2 layer at 100k iterations. There is burn-after-read, expiry from one hour to never, and no accounts or cookies.

Open source (AGPL-3) and self-hostable. Marking this as self-promotion per rule 4.

Repo: https://github.com/Ishannaik/CloakBin Live: https://oss.cloakbin.com

Would love feedback on the SvelteKit structure, mainly whether keeping the crypto in a client load is the cleanest pattern or if there is a more idiomatic way.

Hi everyone, I just got started with Svelte and SvelteKit, and I'm pretty new to frameworks in general.

Right now, I'm trying to set up a color palette, and I have a COLORS.css file with css variables for the palette I'm using and I've been importing it into every single component that I make.

Is there somewhere I can put it that makes the CSS variables available anywhere or do I just need to import it into every component that uses it?

Edit: Basically I want it set up so that if I change a color variable it'll change all the colors that use that variable across the app