Closed compojoom closed 3 months ago
β Deploy successful!
Storybook: https://fix_widget_fee--walletweb.review.5afe.dev/storybook/
Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.
Type | Occurrences | Fixable |
---|---|---|
Errors | 0 | 0 |
Warnings | 0 | 0 |
Ignored | 0 | N/A |
Report generated by eslint-plus-action
This analysis was generated by the Next.js Bundle Analysis action. π€
Page | Size (compressed) |
---|---|
global |
1000.85Β KB (π‘ +78Β B) |
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/settings/cookies |
7.64Β KB (π’ -2Β B) |
1008.49Β KB |
/terms |
11.58Β KB (π‘ +1.56Β KB) |
1012.44Β KB |
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link
is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 79.03% (-0.02% π») |
11624/14709 |
π΄ | Branches | 58.57% (-0.03% π») |
2846/4859 |
π‘ | Functions | 66.03% | 1858/2814 |
π’ | Lines | 80.4% (-0.02% π») |
10479/13033 |
1433 tests passing in 198 suites.
Report generated by π§ͺjest coverage report action from 797a2d8142207e850843763220deb560a6a74f4c
What it solves
Don't display a widget fee on the confirmation screen if it the feature is the order doesn't have any widget fee applied
How to test it
You would need access to config server. Disable widget fee. Make a swap, on the confirmation view you shouldn't see a fee.
Checklist