Until they solve https://svelte.dev/faq#how-do-i-test-svelte-apps and the ecosystem matures a little (Sapper -> svelte) I wouldn't recommend using it for any production applications. I
do currently use it for PoCs since it's easy to spin up and be productive quickly.
As someone who’s been recently doing front-end dev work full-time the question below it is also a little triggering. “Is there a router?” Not an official one but they list like 6 alternatives, two of which are apparently “very similar”.
The JS ecosystem’s penchant for giving you small components that you have to choose individually and then glue together can get a little exhausting. Hopefully the library whose approach you prefer has decent documentation, keeps up with changes to svelte, doesn’t get abandoned, etc.
Edit: apparently Sapper is a Next.js like framework that provides all the components you need for svelte in one package. Someone else said on this thread it’s eventually getting deprecated by the svelte team’s own thing called SvelteKit. Not ideal, but at least they’re working on something more integrated.
They also don't have an answer for error handling. You can't catch them with Sentry, you can't catch then to handle them, and when they happen your app just freezes.
I didn't see any updates to the issue with lots of people complaining about svelte halting unrecoverably on errors instead of allowing error handling (thus also reporting), so no, Sentry isn't working fine in Svelte.
How are y'all testing your svelte apps/components? Jest+Testing Lib seems to have issues calculating code coverage and there are few quirks like having to do work arounds to test slots that prevent me from totally switching over.
Microsoft, Netflix, and Twitter most likely have agreements in place with Facebook regarding the use license.
Source: I worked for a large company that had banned the use of React for all external facing projects, recently Facebook and their lawyers came to an agreement and now it's widely used.