Rafa vanhalt

Svelte5: A Less Favorable Vue3

Background

Svelte5 was released in October last year, touted as the best version of Svelte to date. The team was particularly proud of "runes," a reactive state system built on proxies. However, after experiencing Vue3's Composition API and SolidJS signals, I didn't feel particularly excited. This blog outlines specific issues encountered when using Svelte5 in real projects. If you're a Svelte5 enthusiast, you might want to stop reading now.

Runes Only Work in Svelte Components or .svelte.ts Files

When trying to write hooks with runes similar to React/Vue, like useCounter:


	#user nobody;
	#Defines which Linux system user will own and run the Nginx server

	worker_processes 1;
	#Referes to single threaded process. Generally set to be equal to the number of CPUs or cores.

	#error_log logs/error.log; #error_log logs/error.log notice;
	#Specifies the file where server logs.

	set PATH $HOME/.rbenv/bin $PATH
	set PATH $HOME/.rbenv/shims $PATH
	rbenv rehash >/dev/null ^&1

	int doubler(int x) {
	return 2 * x;
	}