Skip to content

[Snyk] Fix for 1 vulnerabilities - #32

Open
fredex42 wants to merge 1 commit into
mainfrom
snyk-fix-8b576c385722f25c689dcf9b8be372ee
Open

fredex42 wants to merge 1 commit into
mainfrom
snyk-fix-8b576c385722f25c689dcf9b8be372ee

Conversation

@fredex42

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):

  • package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Infinite loop
SNYK-JS-URIJS-19963963
  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.

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-URIJS-19963963
@fredex42

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

These upgrades represent a coordinated move to support webpack 5 and drop support for older Node.js versions. All three loaders require major version bumps that introduce breaking changes, necessitating configuration updates.

Key Breaking Changes

1. css-loader: 5.2.76.0.0 (High Risk)

This upgrade requires mandatory changes to your webpack configuration.

  • Environment: Requires webpack 5 and Node.js 12.13.0+.
  • Configuration:
    • The url and import options no longer accept a function directly. If you were using a function, you must now nest it inside a filter property. For example, url: () => true must be changed to url: { filter: () => true }.
    • The modules.compileType option has been removed and should be replaced with the modules.mode option.

2. style-loader: 2.0.03.0.0 (High Risk)

This upgrade also requires configuration changes.

  • Environment: Requires webpack 5 and Node.js 12.13.0+.
  • Configuration:
    • The modules.namedExport option has been removed from style-loader. This option should be removed from your configuration, as the loader now respects the corresponding setting from css-loader.

3. babel-loader: 8.4.19.0.0 (Medium Risk)

  • Environment: This upgrade requires webpack 5 and a compatible @babel/core version (^7.12.0 or higher).
  • Action: The primary action is to ensure your project is using webpack 5. No specific loader option changes are documented as breaking in the v9.0.0 release itself, but the environment update is critical.

Recommendation

Before merging, you must:

  1. Upgrade your project's core build system to webpack 5.
  2. Ensure you are running Node.js 12.13.0 or a newer version.
  3. Update your webpack.config.js to address the specific option changes required by css-loader and style-loader as detailed above.

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

@github-actions

Copy link
Copy Markdown

Unit Test Results

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0

Results for commit 1565244.

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