svelte-plugins VS Svelte

The previous version of the library (https://github.com/tanepiper/svelte-formula) was written in TS and I found it quite easy to migrate most of the code back

JSDoc. I've just refactored my old library from TS to VanillaJS + JSDoc

I've started moving away from this - in fact this week I've been migrating my old Svelte form library written in TS to a new total Vanilla ESM version without any bundling or building

Seems like you've built something similar to my own library for Svelte - Formula - very nice!

For example in my code here I'm trying to deal with rows being added and removed that themselves are a whole instance of a form, but I had to revert it to where I just use the mutation observer to know a change is happening but still use a querySelector to fetch all nodes - otherwise it became too much to try maintain all the references.

Since I last posted about it here, a lot has been added - first the documentation website is now live and includes a few examples.

The release is considered an alpha version - the API may change and there are still tests and documentation to right - but you can try it our right now in your own project with npm install svelte-formula - any bugs, issues or suggestions please feel free to leave them here

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.