blazor-wasm-maui-winforms-wpf-template VS dotnet-combine

Next I decided to make a Windows desktop version using WebView. I also made a template https://github.com/Jinjinov/blazor-wasm-maui-winforms-wpf-template that is now somewhat obsolete. The biggest problem is loading the data from IndexedDB before the app starts. Blazor WASM allows you to use JsInterop right from the moment you register your services in dependency injection, so you can access IndexedDB immediately, load the user settings and then start the app. WebView doesn't allow you to use JsInterop before Blazor is initialized. This means that if the user chooses a dark UI theme and you save that choice in IndexedDB, the app will load with the default light UI theme, you will read the IndexedDB on the first render and then apply the dark UI theme. The app will flicker for a second.

I made a template for a cross platform Blazor project: https://github.com/Jinjinov/blazor-wasm-maui-winforms-wpf-template But it is a bit outdated now.

Yea, I'm already taking advantage of a few of the new .net 6 features like implicit using statements defined in the csproj file and not declaring namespaces anywhere in any of my code files. I've got my setup to the point where I can hit build in vscode and it runs dotnet-combine to merge all of my code into a single file then runs sed to strip out the Program class declaration and the closing brace so that I can just copy and paste the generated code into the programmable block.