Golang also has a rich ecosystem of external community libraries but
1) the standard library is often enough to get work done (http server, sql, etc)
2) external libraries often would simply sit atop the standard library which is easier to standardise and swap things around
3) the language is quite bare and simple, I was weirded out by the "for" in Go but I now like it. Need to map, filter, or increment counters? Use "for".
4) No need to hesitate between 5 linters or testing libraries, "go" does it so again it's standardised.
As for Svelte, I'm not loving it as much as Go but for frontend, it's just the most "JS/TS" of all without added layer of magic. There is still some, but it's graspable.
The truth about Svelte post of Rich Harris is very much in point about Svelte. It gets out of your way and feels like HTML/JS/CSS + a few thought out features.
You can use a lot of libraries without a wrapper for svelte.
I hope it gets adoption, I would like to work with it. I like React as well and use it but Svelte straight forward in so many situations that I just enden coding instead of thinking about X different ways to solve a problem and that is where I see similarities with Go.
