🌲 Excited to announce our agreement with @Microsoft for 1.4M tonnes of carbon removal through reforestation in Appalachia! We're transforming 25,000 acres of former mine lands into thriving forests, with community and ecosystem co-benefits! 🧵

If you were missing the "I can just reassign a $: statement" capability of Svelte 4 in version 5 - it's back now!

@thdxr Svelte 5 has an excellent migration guide from v4 to v5. It’s way too big to be a cursor rule though. I ended up dumping into Google Gemini large context window and got a phenomenal cursor rule condensed out of it. Nearly no issues anymore. I would recommend to anyone dealing

If you're interested in more details join the discussion on that other site with the blue monarch logo.

I also sent another PR to @izs that would save 96 TB of traffic to the npm registry.

You think removing is-number to save 440 gb is something? I just had a PR merged to save 112 TB! I hope for the sake of everyone's node_modules that we can all compete to get the highest number 😆

The State of JS 2024 survey is out! https://t.co/to6BbGbYED

@sveltejs v5 is out and Storybook 8.4 is ready: ✅ Runes support ✅ Write your stories in Svelte CSF ✅ Insane, next-level Svelte TypeScript support ✅ Zero-config setup from the Svelte CLI If you’ve written stories for Svelte, you can see that Svelte CSF is a big improvement:

Introducing the new Svelte CLI! https://t.co/XvjMteFdEc We’re now offering the ability to setup CSS, formatting, linting, testing, DB querying, auth, i18n, and more. Just run `npx sv create` and follow the prompts.

Announced at Svelte Summit today: - Svelte 5 released - sv, the new Svelte CLI - new https://t.co/Xj49aAyghW website to go live next week - Svelte Hackathon with thousands in prizes See https://t.co/Tq2rTyITGG and https://t.co/lejkJKnZqk for more details

I made a mistake. It's two announcement talks, but... four things being announced! Join us on Saturday:

Note that the query for this chart considers a web page to be client-side rendered if 75% of the HTML is generated on the client side.

Your use case may warrant a client-side rendered SPA. Perhaps you are building a locally-served app or using it in a mobile framework. It's good to have the flexibility to build a SPA, but you should be careful to choose the right tool for the job.

Some data from Google (big thank you to @rick_viscomi and @imkevdev!) Client-side-only SPAs are extremely detrimental to latency as they add a network round-trip before rendering begins. You can win at LCP by making it harder to build client-side apps😉

This is the first time we've had two different announcements to share at the same Svelte Summit. Let the speculation commence!

Now available: npx svelte-migrate svelte-5 Please try it out and file issues in the Svelte repo. Do check that it hasn't already been reported as it's quite new and bound to have bugs.

Thanks to @dummdidumm_ for the work on svelte-check. Not to mention @43081j and @paulmillr for the work on chokidar.

svelte-check has gone from 46 dependencies in v3 down to 9 dependencies in the latest release! This CLI is used by almost every Svelte project.

Btw, this is so much traffic that @thedevminertv had to use https://t.co/jttVLev38i in the reporting tool so that it could calculate it without triggering an integer overflow!

Remember when one usage of is-number caused 440GB/week of traffic to npm? Well the only reason people where using it was because the popular chokidar file watcher did indirectly. chokidar v4 just dropped it and others resulting in a savings of 2.5 TB/week of traffic to npm