Skip to content
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

Dependency update #112

Merged
merged 5 commits into from
Feb 27, 2024
Merged

Dependency update #112

merged 5 commits into from
Feb 27, 2024

Conversation

lzear
Copy link
Owner

@lzear lzear commented Feb 27, 2024

No description provided.

Copy link

changeset-bot bot commented Feb 27, 2024

🦋 Changeset detected

Latest commit: 7f00601

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
demo Patch
votes Patch

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

Copy link

vercel bot commented Feb 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
votes ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 27, 2024 9:58am

Copy link

codecov bot commented Feb 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.96%. Comparing base (1fb3162) to head (7f00601).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #112   +/-   ##
=======================================
  Coverage   97.96%   97.96%           
=======================================
  Files          47       47           
  Lines         589      589           
  Branches       74       74           
=======================================
  Hits          577      577           
  Misses          4        4           
  Partials        8        8           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

Size Change: -16 B (0%)

Total Size: 65.7 kB

Filename Size Change
votes/dist/index.global.js 53.2 kB -5 B (0%)
votes/dist/index.js 6.45 kB -4 B (0%)
votes/dist/index.mjs 6.07 kB -7 B (0%)

compressed-size-action

Copy link
Contributor

📦 Next.js Bundle Analysis for demo

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 199.22 KB (🟡 +6.49 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!

Two 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)
/ 18.14 KB 217.36 KB 62.10% (🟡 +0.02%)
/_error 666 B 199.87 KB 57.11% (+/- <0.01%)
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.

@lzear lzear merged commit f37a07f into master Feb 27, 2024
10 of 11 checks passed
@lzear lzear deleted the deps-updt branch February 27, 2024 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant