[Snyk] Security upgrade jest from 26.6.3 to 28.0.0 #3469
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 fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
packages/internal-lib-build/package.jsonpackages/internal-lib-build/package-lock.jsonThis major version upgrade from Jest 26 to 28 introduces significant breaking changes, including new defaults for the test environment and test runner, removal of packages, and API modifications.
Highlights:
jsdomtonode. For browser-like environment testing,jest-environment-jsdommust now be explicitly installed and configured injest.config.js.testURLconfiguration option has been removed and replaced bytestEnvironmentOptions.url. Thetimersoption was renamed tofakeTimers. Additionally,expectis now a named export instead of a default export.Source: Jest documentation
Recommendation: Follow the official migration guides for v27 and v28. Developers must install
jest-environment-jsdomfor DOM testing and update their Jest configuration files and import statements to align with the new APIs.Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-JSYAML-13961110
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Prototype Pollution