-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mobile menu #469
Mobile menu #469
Conversation
🦋 Changeset detectedLatest commit: 61703fc The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
4 Skipped Deployments
|
📦 Next.js Bundle Analysis for @blobscan/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
264.41 KB (🟡 +18.79 KB) |
Details
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!
Ten Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load | % of Budget (350 KB ) |
---|---|---|---|
/ |
352.23 KB |
616.64 KB | 176.18% (🟢 -4.88%) |
/address/[address] |
26.62 KB |
291.03 KB | 83.15% (🟢 -4.89%) |
/blob/[hash] |
25.31 KB |
289.73 KB | 82.78% (🟢 -4.89%) |
/blobs |
15.76 KB |
280.17 KB | 80.05% (🟢 -4.88%) |
/block/[id] |
11.76 KB |
276.17 KB | 78.91% (🟢 -4.89%) |
/blocks |
13.49 KB |
277.9 KB | 79.40% (🟢 -4.88%) |
/stats/blob |
336.46 KB |
600.87 KB | 171.68% (🟢 -4.81%) |
/stats/block |
337.48 KB |
601.89 KB | 171.97% (🟢 -4.81%) |
/stats/tx |
336.58 KB |
601 KB | 171.71% (🟢 -4.80%) |
/txs |
20.03 KB |
284.44 KB | 81.27% (🟢 -4.88%) |
Details
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
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your 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. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #469 +/- ##
=======================================
Coverage ? 89.83%
=======================================
Files ? 146
Lines ? 9630
Branches ? 1020
=======================================
Hits ? 8651
Misses ? 979
Partials ? 0 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good!
There are some ideas I had in mind for this. I forgot to add the necessary context to this issue :/.
I updated the issue with the design that I had in mind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job!
It’s starting to take shape nicely.
I feel the current components can get some extra refactoring: rename some of them, abstract the side panel logic, restructure them, etc.
apps/web/src/components/AppLayout/TopBarLayout/CompactTopBar.tsx
Outdated
Show resolved
Hide resolved
- Improve components names - Separate `SidebarNavigationMenu` from `NavigationMenus` - Re-add `Menu` component to `NavigationMenus` to keep consistency with `SidebarNavigationMenu to keep consistency with `SidebarNavigationMenu``
…hen the user is on the corresponding URL route
Nice job! I pushed a few commits fixing some extra things. Some things I'd like to point out:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!. Waiting for another approve so we can merge this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good at preview
…ts in `SidebarNavigationMenu`
transition: "transform 0.6s", | ||
}} | ||
> | ||
<div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use <>
fragment instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This component is actually outdated
} | ||
|
||
return ( | ||
<div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<div> | |
<> |
I would use fragment instead as we avoid to add an unnecessary div
in the DOM tree
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This component is actually outdated
Checklist
Description
MobileMenu
component.Related Issue
Closes #436
Screenshots:
Update:
2024-08-01.18-57-20.mp4