You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release includes major version upgrades for the critical eslint and jest packages, introducing significant breaking changes that require developer action. A third package, del-cli, also has a breaking change related to its supported Node.js version.
Top 3 Most Impactful Upgrades
eslint 9.39.1 → 10.0.0 (High Risk)
This is a major upgrade that completely removes the legacy .eslintrc configuration system. All projects must migrate to the new flat configuration file (eslint.config.js). Additionally, support for Node.js versions below 20.19.0 has been dropped. Recommendation: Before merging, you must migrate your ESLint configuration from .eslintrc.js to the new eslint.config.js format. This is a mandatory change. Source: ESLint v10 Migration Guide, Release Notes
jest 29.7.0 → 30.0.0 (High Risk)
This major version drops support for end-of-life Node.js versions (14, 16, 19, 21) and now requires Node.js 18 or newer. It includes several breaking changes:
Deprecated expect aliases (e.g., toBeCalled()) have been removed and must be replaced with their canonical names (e.g., toHaveBeenCalled()).
The underlying jsdom dependency was upgraded, which may affect tests that mock browser environments like window.location.
Snapshot formats have changed, which will require updating existing snapshots. Recommendation: Run tests and update snapshots. Use eslint-plugin-jest to help autofix removed API aliases. Verify tests that rely on JSDOM behavior. Source: Jest 30 Migration Guide, Blog Post
del-cli 5.1.0 → 6.0.0 (Medium Risk)
The primary breaking change in this major version is the requirement of Node.js 18 or later. Projects running on older Node.js versions will need to upgrade their environment. Recommendation: Ensure your deployment and development environments are running Node.js 18 or a newer version. Source: Release notes
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
This file contains hidden or 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
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/koa-tracer/package.jsonpackages/koa-tracer/package-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-MINIMATCH-15309438
Breaking Change Risk
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:
🦉 Regular Expression Denial of Service (ReDoS)