Closed jmealy closed 1 day ago
β Deploy successful!
Storybook: https://single_msg_page--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.21Β KB (π‘ +31Β 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 page was added to the bundle from the code in this PR:
Page | Size (compressed) | First Load |
---|---|---|
/transactions/msg |
29.42Β KB |
1.01Β MB |
The following page changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/transactions/messages |
39.02Β KB (π‘ +1.09Β KB) |
1.01Β MB |
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% (+0.25% πΌ) |
11492/14546 |
π΄ | Branches | 58.21% (+0.17% πΌ) |
2782/4779 |
π‘ | Functions | 65.93% (+0.19% πΌ) |
1838/2788 |
π’ | Lines | 80.35% (+0.21% πΌ) |
10359/12893 |
1415 tests passing in 196 suites.
Report generated by π§ͺjest coverage report action from 771a054f76120b3c3093b6452288718002f92cdf
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
LGTM
The link is fine, it copies the the url properly. Looks good in dark mode and mobile viewports
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
What it solves
Resolves #2020
How this PR fixes it
How to test it
Screenshots
[1] [2]
Checklist