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

chore(deps): update dependency vitest to v2.1.3 #3490

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 2.1.2 -> 2.1.3 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v2.1.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Oct 18, 2024

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

Name Status Preview Comments Updated (UTC)
nextra-theme-docs-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 18, 2024 4:22pm
nextra-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 18, 2024 4:22pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
nextra ⬜️ Ignored (Inspect) Visit Preview Oct 18, 2024 4:22pm

Copy link

changeset-bot bot commented Oct 18, 2024

⚠️ No Changeset found

Latest commit: 5a40410

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

github-actions bot commented Oct 18, 2024

📦 Next.js Bundle Analysis for swr-site

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

Nine 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)
/en/blog 8.64 KB 176.37 KB 50.39% (+/- <0.01%)
/en/docs/advanced/more/tree/three 7.92 KB 175.64 KB 50.18% (+/- <0.01%)
/en/docs/code-block-without-language 8.07 KB 175.79 KB 50.23% (+/- <0.01%)
/en/examples/full 8.17 KB 175.89 KB 50.26% (+/- <0.01%)
/es/docs/conditional-fetching 7.24 KB 174.96 KB 49.99% (+/- <0.01%)
/ru 11.16 KB 178.88 KB 51.11% (+/- <0.01%)
/ru/blog 7.6 KB 175.32 KB 50.09% (+/- <0.01%)
/ru/docs/advanced/file-name.with.DOTS 7 KB 174.72 KB 49.92% (+/- <0.01%)
/ru/docs/understanding 12.5 KB 180.23 KB 51.49% (+/- <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.

Copy link
Contributor

github-actions bot commented Oct 18, 2024

📦 Next.js Bundle Analysis for docs

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

Four Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/docs/guide/advanced 8.71 KB (🟢 1 B) 183.57 KB
/docs/guide/advanced/twoslash-support 9.32 KB (🟢 1 B) 184.18 KB
/docs/guide/organize-files 11.33 KB (-1 B) 186.19 KB
/docs/guide/ssg 7.53 KB (🟢 -1 B) 182.39 KB
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

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 undefined% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 84393a8 to 5a40410 Compare October 18, 2024 16:19
@dimaMachina dimaMachina merged commit f165021 into main Oct 18, 2024
7 of 9 checks passed
@dimaMachina dimaMachina deleted the renovate/vitest-monorepo branch October 18, 2024 16:19
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