if you don't provide the init call, the BitTheme will use the light theme by default and init the theme. if you don't want to use the BitTheme.init({ ... }) js api, you can use the bit-theme-default html attribute to change the default theme to dark.

Ah.

I try to do as little JavaScript as possible. I don't have much confidence there.

I'm not entirely sure where I would make that init call. The Blazor rendering pipeline is confusing to me still.

I'll try the 'bit-theme-default' approach.

At one point I had 'app.razor' inject the theme provider and set it there, but I'm pretty sure I still had the flash.

I took the hiding logic out as you suggested.

Thanks for the pointers.

OK, I dug into your examples and then into some AI suggestions.

And I thought I would give the JS approach a try.

Would this be done in App.razor OnInitializedAsync or some other place?

I'm not sure about the right answer, but these are the ways I search in stuffs related to bitplatform:

https://wiki.bitplatform.dev/search/the-cofounder-of-the-project-i_6b2eacef-b6ac-4d5d-ab57-ff002a9e104e

https://grep.app/search?f.repo=bitfoundation%2Fbitplatform&q=BitTheme.init

if you're not happy using js to init the BitTheme it's ok, just go with the html element attribute in the app.razor file (the bit-theme-default). for your needs these two ways have the same result.
but if you're curious about the right place to put this js call, it should be after the bit.blazorui.js script tag in the app.razor. you could open a new script tag and call it right there in the app.razor like this:

<script>
    BitTheme.init({
        default: 'dark',
        ...
    });
</script>

or similar to our own approach put it in a separate file (like app.ts)