template VS Svelte

This creates a basic Svelte project for us from this template. We still have to install the packages that come with the template though. We can use either yarn or npm for this but I'll use yarn.

I didn't want to use Sveltekit because I don't think I would benefit a lot from things like routing and ssr, which would end up adding unnecessary complexity. I also didn't want to use some of the Svelte templates out there because they point to a repo that is now archived in favour of Vite and/or Sveltekit. Also, since I was at it, I decided to throw in a CSS framework and ended up choosing Tailwind to complete my template, but you could ignore it and go with the svelte way of doing things if you prefer.

https://sveltestrap.js.org/ https://svelte.dev/ https://github.com/sveltejs/template https://svelte.dev/repl/7eb8c1dd6cac414792b0edb53521ab49?version=3.20.1 https://svelte.dev/repl/4162507931ea406c9f03be1b3aed9e94?version=3.48.0

! could not fetch remote https://github.com/sveltejs/template

This. Using the svelte template as OP did, you should have a public directory by default.

Grab your favorite Svelte template. I'm a typescript+pug+stylus weirdo, but the standard Svelte-provided one is a good place to start.

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.

Volar originally was Vue3's language support tool for VScode (I don't know about other editors). By today, volar has become a language indipendent framework to create language tools. It might still be a bit early for the dev with skill issues like me to use it and build some tools, but astro and svelte already use Volar to create their language tools.