sites VS Svelte

Minor correction, svelte repl is in sites repo, and it's well maintained and updated.

I found this GitHub issue that feels relevant to the Svelte REPL issue. It sounds like unpkg doesn't successfully resolve the dependency due to differences between CJS and ESM.

You'd need to bundle the svelte compiler, then feed the compiled output of your string through a worker containing a browser build of rollup to bundle all of the internal dependencies. Have a look at https://github.com/sveltejs/sites/tree/master/packages/repl if you really want to go through with this.

See: https://github.com/sveltejs/sites/issues/113

Here's one built with Svelte: https://hn.svelte.dev/

It's not exactly an apples-to-apples comparison for a number of reasons including implementation and hosting differences, but might be interesting to people anyway. The code lives here: https://github.com/sveltejs/sites/tree/master/sites/hn.svelt...

Assuming you cloned https://github.com/sveltejs/sites, then you need to cd into sites/ (https://github.com/sveltejs/sites/tree/master/sites) and then into the site you want. Afterwards just follow the instructions in the README (usually pnpm i and pnpm run dev).

I'm pretty sure it's just your extension misbehaving. Here is the like to the repo: https://github.com/sveltejs/sites/tree/master/sites/svelte.dev

Hm, it works for me (iOS). Might be worth opening an issue on the site repo with the issue you’re seeing.

the kit.svelte.dev site is also fully open source, but it uses a lot of components which handle almost everything also uses api.svelte.dev, a non-svelte site to get all the data so I don't know how helpful that is either

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.