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

[Snyk] Upgrade @vitest/coverage-c8 from 0.31.4 to 0.32.0 #117

Closed
wants to merge 1 commit into from

Conversation

u-sho
Copy link
Owner

@u-sho u-sho commented Jul 2, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @vitest/coverage-c8 from 0.31.4 to 0.32.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released a month ago, on 2023-06-06.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-WORDWRAP-3149973
372/1000
Why? Proof of Concept exploit, CVSS 5.3
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: @vitest/coverage-c8
  • 0.32.0 - 2023-06-06

       🚨 Breaking Changes

    • Throw an error, if the module cannot be resolved  -  by @ sheremet-va in #3307 (1ad63)
      • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
    • Improve globs  -  by @ nickmccurdy in #3392 (19ecc)
      • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
    • Add @ vitest/coverage-v8 package  -  by @ AriPerkkio in #3339 (82112)
      • Vitest now uses v8 code coverage directly for better performance. @ vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @ vitest/coverage-v8 package if you previously used @ vitest/coverage-c8.
    • mocker: Don't restore mock to the original if the module is automocked  -  by @ sheremet-va in #3518 (c1004)
      • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.

       🚀 Features

       🐞 Bug Fixes

        View changes on GitHub
  • 0.31.4 - 2023-06-01

       🚀 Features

       🐞 Bug Fixes

        View changes on GitHub
from @vitest/coverage-c8 GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@vercel
Copy link

vercel bot commented Jul 2, 2023

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

Name Status Preview Comments Updated (UTC)
quantum-game-arena ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 2, 2023 2:40pm

@u-sho
Copy link
Owner Author

u-sho commented Jul 2, 2023

@vitest/coverage-c8 is deprecated.
cf. vitest@v0.32.0 (vitest/#3339)

@u-sho u-sho closed this Jul 2, 2023
@u-sho u-sho deleted the snyk-upgrade-c92e344fbd6a73e382d8b4c2191897c2 branch July 2, 2023 16:48
@u-sho u-sho mentioned this pull request Jul 2, 2023
@u-sho u-sho added dependencies Pull requests that update a dependency file duplicate This issue or pull request already exists labels Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants