awesome-wasm-tools VS awesome-blazor

One approach that I find interesting is to use Wasm because it was designed as a portable execution format for lots of language types. It has an amazing amount of flexibility for byte working and execution.

It is fairly trivial to see all of main memory and single step execution of a wasm program. If one runs wasm3 in wasm3, you can then trace the inner interpreter as well. Check out the section on trace visualization.

https://github.com/vshymanskyy/awesome-wasm-tools

Since I don’t know what theme constraints you might have, I’d check out this and go to the ‘Component Bundles’ section under ‘Libraries and Extensions’. There are some good open source component libraries that should offer at least one good date picker alternative that you could drop in for the licensed one causing you issues.

Querying a (MySQL) database can be done in multiple ways in .NET, I usually prefer to use Entity Framework Core. For components, I like to use the MudBlazor component library. It also has an autocomplete component. If you want to look at different options for Blazor libraries/components(and more) you can take a look at this awesome collection.

Anyhow, there are a few similar sites at https://blazorschool.com/ and https://blazor-university.com/ , and if you're serious about it there are a ton of resources catalogued at https://github.com/AdrienTorris/awesome-blazor

https://github.com/AdrienTorris/awesome-blazor, specifically under the Libraries & Extensions section.

It is usually true that Microsoft's documentation falls behind their implementations, but it does eventually catch up. But this: https://docs.microsoft.com/en-us/aspnet/core/blazor/?view=aspnetcore-6.0 isn't all that bad. There are a lot of resources here https://github.com/AdrienTorris/awesome-blazor too.