[Snyk] Upgrade: , javy, vitest #48
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade:
- @shopify/shopify_function from 0.0.3 to 0.3.0.
See this package in npm: https://www.npmjs.com/package/@shopify/shopify_function
- javy from 0.1.0 to 0.1.2.
See this package in npm: https://www.npmjs.com/package/javy
- vitest from 0.29.8 to 2.0.5.
See this package in npm: https://www.npmjs.com/package/vitest
See this project in Snyk:
https://app.snyk.io/org/cachiman/project/06c22f1a-0f68-4792-83c7-c743a6a1c741?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.ℹ️ 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.
@shopify/shopify_function
⚠️ This is a major version upgrade, and may be a breaking change | 2 months ago
from 0.0.3 to 0.3.0 | 3 versions ahead of your current version | 3 months ago
on 2024-06-19
javy
from 0.1.0 to 0.1.2 | 2 versions ahead of your current version | a year ago
on 2023-07-28
vitest
from 0.29.8 to 2.0.5 | 65 versions ahead of your current version
on 2024-07-31
Release notes
Package name: vitest
🚀 Features
🐞 Bug Fixes
testNamePatternadds leading space - by @ AriPerkkio in #6186 (073a5)afterEachcleanup hooks in node entrypoint - by @ sheremet-va in #6192 (e6fbc)defineProjectanddefineWorkspacetypes - by @ sheremet-va in #6198 (8cd82)node:*imports in__mocks__folder - by @ sheremet-va in #6204 (a48be)View changes on GitHub
🐞 Bug Fixes
require- by @ sheremet-va in #6159 (807a2)*.ctsfiles - by @ AriPerkkio in #6189 (5da45)thresholds.<glob>.100option - by @ thor-juhasz and @ AriPerkkio in #6174 (f6845)mockImplementationfor function overload and unions - by @ hi-ogawa in #6181 (7a75b)View changes on GitHub
🚀 Features
🐞 Bug Fixes
--inspect-brkstop on Windows - by @ AriPerkkio in #6110 (f8519)vi.spyOntoMockInstanceof function overload - by @ hi-ogawa in #6086 (e9f9a)View changes on GitHub
🐞 Bug Fixes
crypto.randomUUIDfrom the client - by @ userquin in #6079 (04c83)vitest- by @ AriPerkkio in #6060 (95a2d)🏎 Performance
View changes on GitHub
🐞 Bug Fixes
View changes on GitHub
Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.
🚨 Breaking Changes
--segfault-retry- by @ sheremet-va in #5514 (ed60e)threadssegfaults. Our current recommendation is to use the new defaultforkspool instead.onTestFinishedhook. This can make your tests run a little bit slower.coverage.ignoreEmptyLinesby default - by @ AriPerkkio in #5543 (31994)locationfield pointed to the error location instead of the test location. Now it is aligned with jest and contains thelineandcolumnof a test function, but requiresincludeTaskLocationto be enabled.poolto'forks'- by @ AriPerkkio in #5047 (7f8f9)threadspool: https://vitest.dev/guide/improving-performance.html#pool--merge-reportsto support coverage - by @ AriPerkkio in #5736 (b7438)spy.mock.returns. If the function is async or returns a promise, it will always succeed and have aPromiseinresults. To make migration easier, we introducedspy.mock.settledResultsthat unwraps promises andexpect().toHaveResolved()matcher that accepts unwrapped value.jsonoutput - by @ sheremet-va in #5802 (dd754)indexScriptstoorchestratorScriptsin the browser config - by @ sheremet-va in #5842 (49f34)poolAPI - now requirescollectTestsmethod alongsiderunTests.excludein coverage - by @ AriPerkkio in #5997 (169bc)excludepatterns ifcoverage.excludewas overridden in the config. Add your test patterns manually, or merge your overrides with default ones:['**/my-pattern.js', ...coverageConfigDefaults.exclude]. See https://vitest.dev/config/#coverage-exclude for an example.process.exitif workspace project failed to be created - by @ sheremet-va in #5804 (a820e)process.exitmanually - by @ sheremet-va in #5926 (e9b63)🚀 Features
clickevent - by @ sheremet-va in #5777 (839c3)page.screenshotmethod - by @ sheremet-va in #5853 (81c42)userEventmethods, addfillanddragAndDropevents - by @ sheremet-va in #5882 (4dbea)expect.dommethod and bundlejest-dommatchers with@ vitest/browser- by @ sheremet-va in #5910 (3a96a)tripleClickto interactive api - by @ userquin in #5987 (200a4)