Skip to content

[Snyk] Fix for 1 vulnerabilities - #69

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

Dala0 wants to merge 1 commit into
mainfrom
snyk-fix-fcb2d3651c1b3a15104fcb2712fcc563

Conversation

@Dala0

@Dala0 Dala0 commented Sep 21, 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):

  • 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.

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

Dala0 commented Sep 21, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This upgrade includes multiple major versions with significant breaking changes, requiring configuration and potentially code modifications. The highest risks come from ajv, which has been upgraded across two major versions, and css-loader, which now requires webpack 5 asset modules.

Top 3 Most Impactful Upgrades

1. ajv: 6.12.6 → 8.15.0 (HIGH RISK)

This is a jump across two major versions (v7 and v8) and includes a complete rewrite of the library. Expect significant migration effort.

  • Strict Mode by Default: Ajv v7 introduced a strict: true mode by default, which is much less permissive and may cause existing schemas to fail validation for issues that were previously ignored. [10, 16]
  • JSON Schema draft-04 Removed: Support for the older draft-04 specification has been removed. Schemas using it must be migrated. [8, 11]
  • Formats Extracted: Validation for formats (e.g., date-time, email) is no longer included by default. You must now install and configure the ajv-formats package separately. [8, 11]
  • API Changes: The new keyword is now mandatory when creating an instance (new Ajv()), and the API for adding custom keywords has changed. [3]

Recommendation: Carefully review the Ajv v7 and v8 migration guides. Audit all existing JSON schemas for compatibility with the new strict mode and ensure you add ajv-formats if you rely on format validation.

2. css-loader: 5.2.6 → 6.0.0 (HIGH RISK)

This upgrade modernizes the loader to align with webpack 5 features.

  • Webpack 5 & Node.js 12+ Required: This version requires webpack 5 and Node.js 12.13.0 or newer. [2]
  • Asset Modules Required: file-loader and url-loader are now deprecated. css-loader v6 generates new URL(...) syntax, which relies on webpack 5's built-in Asset Modules for handling images, fonts, and other assets referenced in CSS. Your webpack configuration must be updated from using file-loader/url-loader to using type: 'asset'. [2]
  • ~ Alias Deprecated: Using ~ to reference modules in node_modules (e.g., @import '~package/style.css') is deprecated and should be removed. [2]

Recommendation: Update your webpack configuration to use Asset Modules instead of file-loader or url-loader for assets referenced by CSS. Remove the ~ prefix from imports.

3. style-loader: 2.0.0 → 3.0.0 (MEDIUM RISK)

  • Webpack 5 & Node.js 12+ Required: This version requires webpack 5 and Node.js 12.13.0 or newer. [5, 15]
  • ES Modules by Default: The esModule option is now true by default. This may require changing style imports from const locals = require('./styles.css') to import locals from './styles.css'. [5]

Other Upgrades

  • webpack: 5.38.1 → 5.98.0 (Low Risk): As your project is already on webpack 5, this upgrade consists of minor enhancements and bug fixes without major breaking changes. The most significant breaking changes, like the removal of Node

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 ccd007f.

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