Fix CSS Hot Reload - Handle fingerprint when hot reloading scoped CSS bundles #27788
+12
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
This is for MAUI Blazor Hybrid apps. CSS Hot Reload from Visual Studio wasn't working for scoped CSS files that come from Razor Class Libraries.
During the build, the scoped CSS files get built into a bundle called:
LibraryName.<fingerprint>.bundle.scp.css
At runtime, CSS Hot Reload will trigger a scoped CSS build, which outputs:
LibraryName.bundle.scp.css
Fingerprints are not included during that part of the build. This fix will match the original fingerprinted name to the newly built name and allows CSS hot reload to work.
This was the PR that introduced fingerprinting:
Issues Fixed