ComputerGuy

New in Svelte: Comments inside component/element tags!

you know what to do --> npmx.dev/package/svelte

wikipedia turns 25 today! the last unenshittified major website! backbone of online info! triumph of humanity! powered by urge of unpaid randos to correct each other! somehow mostly reliable! "good thing wikipedia works in practice, because it sure doesn't work in theory" - old wiki adage

CVEs affecting the Svelte ecosystem Time to upgrade

We've released fixes for 5 CVEs affecting the Svelte ecosystem. Please upgrade your apps!

Read the post to learn if you're affected:

svelte.dev/blog/cves-af...

anakin/padme meme anakin: we're on the front of hacker news padme: because we shipped something good? anakin: padme: something good, right?

guy who pronounces ".png" as "dot pinge"

a variation of the "we should improve society somewhat." vs "yet you participate in society. very curious! i am very intelligent." sketch with the heckler's quotes replaced by the xkcd standards comic

chore: use pkg.imports for builder.js (#15785) · sveltejs/svelte@4f8708a * chore: use pkg.imports for builder.js * use pkg.imports instead of tsconfig * #client/constants

we've been using this in the svelte codebase for a while
github.com/sveltejs/sve...

A package was actually made for this alias so you can write `npm isntall thatgreat`: www.npmjs.com/package/that...

CSS is so powerful now, it's amazing looking through older CSS and seeing what can be replaced with a one-liner. I'm on the hunt for snippets that used to be multiple lines of CSS that can now be done in one. Show me what you got!

Yes! Let's set the record straight. Biome has very little support for Svelte. It's marketing gone overboard. It has no Svelte-specific rules that I'm aware of. I don't think it will ever be a competitive offering. My eyes are on oxlint, which is working towards being able to run eslint-plugin-svelte

A bar chart showing CPU benchmarks. SvelteKit is showing a 7-10x speed up compared to Next.js.

Oh... what's this, you ask? Just a benchmark that coincidentally shows how fast SvelteKit is compared to Next.js 🤷‍♂️

How fast, you ask? Just 7-10x. No biggie.

Svelte ❤️

YouTube video by CultRepo Vite: The Documentary

"Let's hear it for the UN of Javascript!

Vite: The Documentary is finally here.

If you missed the premiere, it's OK!!! Here's the link so you can watch it again, and again and again.

youtu.be/bmWQqAKLgT4 "

Async SSR · sveltejs svelte · Discussion #16784 The Svelte team has been hard at work on asynchronous rendering, with client-side support and remote functions as our first two efforts. It’s time for the third: SSR. Background There are three cor...

Super excited to announce the experimental release of asynchronous SSR in Svelte! github.com/sveltejs/sve...

`await` expressions in your Svelte components can now be rendered on the server, meaning you don't need to render them inside boundaries with a `pending` snippet. Next up, streaming SSR!

Definitely, I'm working on a project that would very much benefit from this. Currently I'm just waiting for Import Bytes to be standardized to use that.

Interesting! So sources have a reactions array, while effects don't know their dependencies? Or is it the other way around?

This is really cool! Looking at the source code, I can definitely see how Svelte influenced it 😄
You said in your other post that it doesn't use signals, what does it use? The code looks very signal-esque...

screenshot of the release PR for SvelteKit remote functions

we just released SvelteKit remote functions. feel like 'minor change' undersells it a little tbh

✅ await in components svelte.dev/docs/svelte/...
✅ remote functions svelte.dev/docs/kit/rem...
🔜 async SSR

truly can't wait to ship the rest of this stuff

Compile Svelte 5 in your head Background5 years ago, I wrote Compile Svelte in your head. That was written for Svelte 3.But now, almost 1 year into Svelte 5 release, which introduce tons of new features, such as runes, fine-graine...

New post in a very long while

lihautan.com/compile-svel...

Async Svelte has released in v5.36.0!
github.com/sveltejs/sve...

That's why migration scripts exist. A while ago, I wrote a component in Svelte 1 and tried to migrate it to Svelte 5 using migration scripts provided by Svelte; the only diff between what I expected and what resulted was state was declared via $props, bc state and props were the same before v3.

You could try using a Portal: github.com/romkor/svelt...

I'm not saying React is bad by any means. All I'm stating is how different React really is from pretty much every other framework, and showing how much it has changed over the past decade, both in its features and goals.

This is also why Signals don't really work in React and React-adjacent frameworks. Fine-grained reactivity doesn't make sense when the component tree gets recreated on every state change.

React uses functions in a more mathematical sense rather than a software sense— functions represent the state of your application at any point in time, and regular optimizations don't account for this. The internal mechanisms of hooks would be infeasible in almost any other framework.

Not to mention that the reason the React Compiler needs to exist is simply because of all the new concepts and abstractions React provides. Regular optimizations wouldn't have the same effect on React code since it doesn't make use of JS like most frameworks.

Things like Hooks and Suspense have their own vocabulary and concepts. Additionally, React tries pretty hard to make it feel like you're using the DOM, with concepts like JSX, when in actuality you are using a thick layer of abstraction between what you're writing and what appears in the DOM.

React originally tried to reduce the vocabulary needed to understand how to use it, but I feel that it has been moving away from that over the past decade. IIRC Pete Hunt mentioned all the vocabulary AngularJS had created/redefined to describe its concepts and implied that React would reduce this.

"React. I know people are not gonna agree. But react is the lord of leaky abstractions. You have to do everything The React Way™. Otherwise you're out of luck. Solid, Svelte, Vue, and most other frameworks only provide abstractions on top of the web. React tries to reinvent it. And while that comes with the upside of things like React Native being able to target any platform/SDK quite trivially, it still means that you're never really using the platform. you're using React. And using React feels like shit."

I just read this comment on a reddit thread about what framework is the closest to vanilla JS and it made me really think about how large of an abstraction React really is. 🧵

"It's a Yes or No Question"