I’ve created yet another @svelte.dev i18n library, specifically designed for @sveltiacms.app. It replaces svelte-i18n and uses MessageFormat 2 to handle complex pluralization, which is essential for many languages.
🎉 We're excited to finally announce TinyBase v8.1 - the one with native Svelte 5 support.
We've got Svelte demos, guides, and a getting-started tool. Links below!
This was fun and we want to give a huge shout out to the @svelte.dev community for being so helpful and supportive!
Bar so tiny you need glasses for SvelteKit
It's getting smaller in SvelteKit 3!
Token efficiency of many frameworks vs svelte 5 as baseline
One thing I thought might be cool would be to make some of the functionality live in plugins. E.g. the Slack library pulls in 115 dependencies, but if you're not using the Slack notification feature then you probably don't need them
npmgraph.js.org?q=@slack/bolt
I just took my first brief look at the OpenClaw repository and I was shocked.
5,000 open PRs, 500 dependencies, 250 security issues! 😱
I can't imagine trying to manage a project that gets so popular so quickly.
Who here is on Svelte 4 yet?
Curious to hear what is stopping you from upgrading to Svelte 5, and if we can make things any easier here.
You will need to upgrade to `@sveltejs/vite-plugin-svelte` version 7 when upgrading to version 8. Minimal code changes should be required and would be covered in the Vite migration guide as @fubits.dev mentioned
SvelteKit 2 now fully supports Vite 8
SvelteKit 3 will require it - giving additional optimizations and functionality. E.g. SvelteKit 3 will use @rolldown.rs hook filters to spend more compilation time in rust and less in JavaScript. And SvelteKit 3 adapters use only rolldown without esbuild
Me too! It's "ski week" here in the US and I've made my first visit to Idaho
Remote functions will be the biggest game changer
The Vite environment API and Cloudflare + Netlify work may enable adapters to be used in development, which will be big if you're using platform-specific stuff with those adapters
A big one will be adopting Vite's new environment API. The teams from Cloudflare and Netlify are really actively contributing and those adapters will get more powerful. Lots of work is happening on remote functions. Requiring a newer version of Node for fewer and newer dependencies
Starting to merge PRs for SvelteKit 3!
A long road ahead, but excited to get started!
github.com/sveltejs/kit...
Happy to report that the Chatto development instance is now available for testing. Go nuts (but not too nuts, k?)
The Immich photo manager is written in Svelte!
No biggie - just 1-step better-auth setup for Svelte 🔥.
Kudos @jyc.dev. I was really really hoping for this to become reality one day!
github.com/sveltejs/cli...
It's official, you can now get paid up to $10,000 for finding security issues in Svelte and SvelteKit! Big thanks to both the security team at Vercel and the Svelte maintainers' group for coming together to make this possible. Learn more: vercel.com/blog/the-ver...
Success message and celebration reaction for sveltekit passing vite-ecosystem-ci with vite-8 beta for the first time
It took a while, lots of debugging and fixes in rolldown, vite-plugin-svelte and sveltekit, but today it happened. For the first time, sveltekit tests in vite-ecosystem-ci for vite-8 beta passed.
github.com/vitejs/vite-...
Thanks to everyone who helped getting there especially @sapphi.red
I haven't heard the phrase "reward early, punish late" before. Would you be able to share an example of what the API is now vs what you'd like it to be?
npmjs.com used to link to the package directory when it was contained in a sub-directory of a monorepo. It no longer does and makes me so angry that they made the UI purely worse when they changed it
One of these is not like the others. I believe `$lib` should work as I demonstrated because it's just a Typescript alias. `$app` and `$env` however are Vite virtual modules and won't work without Vite unfortunately.
