Skip to content

[Snyk] Fix for 1 vulnerabilities - #162

Open
Dala0 wants to merge 1 commit into
mainfrom
snyk-fix-29effa0544f70cf05193d17aaf53bff0
Open

Dala0 wants to merge 1 commit into
mainfrom
snyk-fix-29effa0544f70cf05193d17aaf53bff0

Conversation

@Dala0

@Dala0 Dala0 commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

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

Snyk changed the following file(s):

  • frontend/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

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.

@Dala0

Dala0 commented Sep 20, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This upgrade involves major version bumps for css-loader and style-loader which introduce significant breaking changes. The webpack upgrade is minor and considered low risk.

css-loader@5.2.4 → css-loader@6.0.0 (High Risk)

This is a major version upgrade with several breaking changes that require configuration updates.

Key Changes:

  • Node.js and webpack versions: Requires a minimum Node.js version of 12.13.0 and webpack 5.
  • Asset Handling: file-loader and url-loader are now deprecated. css-loader v6 is designed to work with webpack 5's built-in Asset Modules. You will need to update your webpack configuration to replace these loaders with type: 'asset'.
  • esModule Default: The esModule option is now true by default.
  • Pathing: Using ~ in @import or url() paths to resolve modules is deprecated and should be removed (e.g., url(~package/image.png) becomes url(package/image.png)).

Recommendation: Review your asset handling configuration and migrate from file-loader/url-loader to webpack's native Asset Modules. Remove any usage of the ~ prefix in CSS paths.

style-loader@2.0.0 → style-loader@3.0.0 (High Risk)

This major version upgrade aligns style-loader with webpack 5.

Key Changes:

  • Node.js and webpack versions: Requires a minimum Node.js version of 12.13.0 and webpack 5.
  • Option Removal: The modules.namedExport option has been removed. The loader now automatically respects the corresponding option from css-loader.

Recommendation: Ensure your environment meets the new Node.js and webpack version requirements. Remove the modules.namedExport option from your style-loader configuration.

webpack@5.89.0 → webpack@5.98.0 (Low Risk)

This is a minor version update within webpack 5. The release notes for this range primarily contain bug fixes, performance improvements, and non-breaking feature additions. No breaking changes are documented for this specific version span.

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 34d5a81.

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