Skip to content

[Snyk] Fix for 1 vulnerabilities#329

Open
rvu-snyk wants to merge 1 commit into
masterfrom
snyk-fix-95cec9bfe68544652aa6a2833b36ca94
Open

[Snyk] Fix for 1 vulnerabilities#329
rvu-snyk wants to merge 1 commit into
masterfrom
snyk-fix-95cec9bfe68544652aa6a2833b36ca94

Conversation

@rvu-snyk

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • packages/koa-prometheus/package.json
  • packages/koa-prometheus/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650
  721  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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.

…ackage-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-BRACEEXPANSION-17706650
@rvu-snyk

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This update includes major version upgrades for both @babel/cli and eslint, introducing significant breaking changes that require developer action.

@babel/cli@7.28.6 → @babel/cli@8.0.0

Risk: HIGH

Babel 8 modernizes its core but requires configuration updates. The most impactful changes are:

  • Default Target Changed: Babel no longer compiles to ES5 by default. It now targets modern browsers based on Browserslist's defaults query (roughly ES2023). If you need to support older environments, you must explicitly define your targets.
  • ESM-Only Package: Babel's internal packages are now ESM-only. This primarily affects tooling and plugin authors but is a core architectural change.
  • Node.js Requirement: Requires a modern version of Node.js (e.g., Node.js 22+).
  • Configuration Changes:
    • The loose and spec options in @babel/preset-env are deprecated in favor of the assumptions option.
    • Polyfill injection via useBuiltIns in @babel/preset-env has been removed and extracted into a separate package, babel-plugin-polyfill-corejs3.
    • The default runtime for @babel/preset-react is now "automatic" instead of "classic".

Recommendation: Review your .babelrc or babel.config.js. Explicitly set the targets option if you support older browsers. Migrate from loose/spec to assumptions and update your polyfill strategy if needed.

Source: Babel 8 Migration Guide, Babel 8 Release Post

eslint@9.39.4 → eslint@10.0.0

Risk: HIGH

ESLint 10 completes the transition to the "flat config" system, making it mandatory.

  • eslintrc Removed: The legacy configuration format (.eslintrc.js, .eslintrc.json) is no longer supported. All projects must migrate to a eslint.config.js file.
  • Node.js Requirement: Support for Node.js versions older than 20.19.0 has been dropped.
  • New Config Lookup: The engine now finds eslint.config.js by searching up from each linted file's directory, improving behavior in monorepos.
  • eslint:recommended Updated: The recommended ruleset has been updated, which may cause new linting errors to appear after upgrading.

Recommendation: Use the official migration script (npx @eslint/migrate-config) to convert your existing .eslintrc file to the new eslint.config.js format. Update your Node.js version if it is below v20.19.0.

Source: ESLint v10 Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants