Nate servusdei2018

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:

Regular Colors

Value	Color
\e[0;30m	Black
\e[0;31m	Red
\e[0;32m	Green
\e[0;33m	Yellow
\e[0;34m	Blue
\e[0;35m	Purple

ANSI Escape Sequences

Standard escape codes are prefixed with Escape:

Ctrl-Key: ^[
Octal: \033
Unicode: \u001b
Hexadecimal: \x1B
Decimal: 27

	package main

	import (
	"flag"
	"fmt"
	)

	var (
	N uint64
	)

	[test]: Update test/* files
	[dist]: Changes to submodules, version bumps, updates to package.json
	[minor]: Small changes
	[doc]: Updates to documentation
	[fix]: Bug fixes
	[bin]: Update binary scripts associated with the project
	[refactor]: Refactor of existing code
	[nit]: Small code review changes mainly around style or syntax
	[feat]: New features


	// Using this code, we can retrieve an image from a user's filesystem, resize the image, and then upload the image
	// to a server using AJAX. Because we use base64 encoding, we can just include the image data as just another string value
	// in a JSON payload.

	// So we can use AJAX to send the file to a server, which is convenient.

	// We have one line of relevant html
	// get file in the first place => <input type="file" custom-on-change="onAcqImageFileChange" class="form-control">