Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I've followed the steps described in https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-10.0?view=aspnetcore-9.0#client-side-fingerprinting

Observations

JS files get fingerprinted correctly during development:

<script src="js/app.o25joi0f6u.js"></script>
<script src="_framework/blazor.webassembly.md9yvkcqlf.js"></script>
<script src="_content/MudBlazor/MudBlazor.min.shgs22i5w1.js"></script>

After publishing, only the framework JS files get fingerprinted:

<script src="js/app.js"></script>
<script src="_framework/blazor.webassembly.md9yvkcqlf.js"></script>
<script src="_content/MudBlazor/MudBlazor.min.js"></script>

CSS files never get fingerprinted:

<link href="_content/MudBlazor/MudBlazor.min.css" rel="stylesheet">
<link rel="stylesheet" href="css/app.css">

I expect this to work because fingerprinting on a hosted app using @Assets["css/app.css"] works just fine. IMHO there should be feature parity for the type of assets that can be fingerprinted.

Expected Behavior

• CSS files get fingerprinted
• All files gets correctly fingerprinted after publishing

Steps To Reproduce

Have a look at this PR:

meenzen/steam-tools#144

It is deployed to Cloudflare Pages, so you can easily see how only the framework js files are fingerprinted by opening the app in your browser:
meenzen/steam-tools#144 (comment)

Exceptions (if any)

No response

.NET Version

10.0.100-preview.4.25258.110

Anything else?

No response