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 upgrade includes several major version bumps with significant breaking changes, most notably for the glob package. Developer action is required to address API changes and ensure environment compatibility.
Top 3 Most Impactful Upgrades
1. glob: 7.2.0 → 12.0.0 (HIGH RISK)
This is a substantial upgrade across five major versions, introducing numerous breaking changes. A significant refactoring effort will be required.
API Rewrite: Version 9.0.0 was a complete rewrite, replacing the callback-based API with a Promise-based API. All glob calls must be updated to use async/await or .then().
Path Separators: As of v8.0.0, backslashes (\) are treated exclusively as escape characters. All glob patterns must use forward-slashes (/) as path separators, which is a critical change for Windows environments.
Node.js Requirement: Support for older Node.js versions has been progressively dropped. The final version requires at least Node.js v16, with v11+ recommending Node.js v20.
Removed Options: Options such as silent, strict, nonull, and nounique have been removed in v9.0.0.
Recommendation: This upgrade requires a dedicated refactoring effort. All usages of glob must be identified and updated to the new Promise-based API, and all patterns must be verified to use forward-slashes. Ensure the project's Node.js version meets the new requirements.
2. grunt: 1.4.1 → 1.6.1 (MEDIUM RISK)
This upgrade introduces breaking changes related to the runtime environment and command-line usage.
Node.js Requirement: Version 1.6.0 and later require Node.js v16+.
CLI Flag Change: Version 1.4.0 replaced the --require command-line flag with --preload. Any scripts using grunt --require must be updated.
3. grunt-contrib-compress: 1.6.0 → 2.0.0 (MEDIUM RISK)
This major version upgrade primarily involves an environment change.
Node.js Requirement: Version 2.0.0 requires
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):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-BRACEEXPANSION-17706650
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:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.