fix(ui): resolve frontend build warnings#850
Open
manichandra wants to merge 1 commit into
Open
Conversation
|
CLA Assistant Lite bot: I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request |
Author
|
I have read the CLA Document and I hereby sign the CLA |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
This resolves frontend production build warnings caused by CSS extraction order conflicts in the insight detail page.
The change aligns component import order so shared CSS modules are loaded consistently across the insight detail chunk.
Which issue(s) this PR fixes:
Fixes #784
Validation
npm run lintnpm run buildmake lintNote:
make testwas attempted locally. Go 1.22.12 failed on macOS withdyld: missing LC_UUID load command; Go 1.26.3 progressed further but hit existingbytedance/mockeyruntime compatibility errors unrelated to this UI-only change.