chore(deps): Remove Unsed UI dependencies
Removed below 3 packages as they are not being used. This helps us reduce bundle size and maintain only used packages
- jwt-decode
- normalize.css
- rxjs-compat
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mayuka-c Once this PR has been reviewed and has the lgtm label, please assign shu-mutou for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 35.21%. Comparing base (4940626) to head (6633197).
:x: Your project check has failed because the head coverage (35.21%) is below the target coverage (75.00%). You can increase the head coverage or adjust the target coverage.
Additional details and impacted files
@@ Coverage Diff @@
## master #10425 +/- ##
=======================================
Coverage 35.21% 35.21%
=======================================
Files 306 306
Lines 12431 12431
Branches 202 183 -19
=======================================
Hits 4378 4378
- Misses 7789 7842 +53
+ Partials 264 211 -53
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
/label kind/cleanup
@mayuka-c: The label(s) /label kind/cleanup cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?
In response to this:
/label kind/cleanup
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.