Skip to content

[Snyk] Upgrade css-loader from 6.8.1 to 7.1.2 #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

@nerdy-tech-com-gitub nerdy-tech-com-gitub commented Jul 12, 2025

snyk-top-banner

Snyk has created this PR to upgrade css-loader from 6.8.1 to 7.1.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 8 versions ahead of your current version.

  • The recommended version was released a year ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-CROSSSPAWN-8303230
44 Proof of Concept
high severity Denial of Service (DoS)
SNYK-JS-HTTPPROXYMIDDLEWARE-8229906
44 Proof of Concept
medium severity Improper Input Validation
SNYK-JS-NANOID-8492085
44 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-8482416
44 Proof of Concept
medium severity Cross-site Scripting (XSS)
SNYK-JS-SERIALIZEJAVASCRIPT-6147607
44 Proof of Concept
medium severity Cross-site Scripting (XSS)
SNYK-JS-COOKIE-8163060
44 No Known Exploit
medium severity Always-Incorrect Control Flow Implementation
SNYK-JS-HTTPPROXYMIDDLEWARE-9691387
44 No Known Exploit
medium severity Improper Check for Unusual or Exceptional Conditions
SNYK-JS-HTTPPROXYMIDDLEWARE-9691389
44 No Known Exploit
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-9789073
44 Proof of Concept
Release notes
Package name: css-loader
  • 7.1.2 - 2024-05-22

    7.1.2 (2024-05-22)

    Bug Fixes

    • keep order of @ imports with the webpackIgnore comment (#1600) (76757ef)
  • 7.1.1 - 2024-04-10

    7.1.1 (2024-04-10)

    Bug Fixes

    • automatically rename class default to _default when named export is enabled (#1590) (d6c31a1)
  • 7.1.0 - 2024-04-08

    7.1.0 (2024-04-08)

    Features

    • added the getJSON option to output CSS modules mapping (#1577) (af834b4)
  • 7.0.0 - 2024-04-04

    7.0.0 (2024-04-04)

    ⚠ BREAKING CHANGES

    • The modules.namedExport option is true by default if you enable the esModule option

    Migration guide:

    Before:

    import style from "./style.css";

    console.log(style.myClass);

    After:

    import * as style from "./style.css";

    console.log(style.myClass);

    Typescript migration:

    Before:

    declare module '*.module.css' {
      const classes: { [key: string]: string };
      export default classes;
    }

    After:

    declare module '*.module.css' {
      const classes: { [key: string]: string };
      export = classes;
    }
    • The modules.exportLocalsConvention has the value as-is when the modules.namedExport option is true and you don't specify a value
    • Minimum supported webpack version is 5.27.0
    • Minimum supported Node.js version is 18.12.0

    Features

    • The modules.namedExports option works fine with any modules.exportLocalsConvention values (f96a110)
    • Added dashed variants for the modules.exportLocalsConvention options (40e1668)
  • 6.11.0 - 2024-04-03

    6.11.0 (2024-04-03)

    Features

    Bug Fixes

    • do not break @ scope at-rule without params (#1581) (e022e3b)
  • 6.10.0 - 2024-01-30

    6.10.0 (2024-01-30)

    Features

    • add @ rspack/core as an optional peer dependency (#1568) (3924679)
    • pass the resourceQuery and resourceFragment to the auto and mode callback (#1569) (d641c4d)
    • support named exports with any characters (6f43929)
  • 6.9.1 - 2024-01-18

    6.9.1 (2024-01-18)

    Bug Fixes

    • css nesting support
    • @ scope at-rule support
  • 6.9.0 - 2024-01-09

    6.9.0 (2024-01-09)

    Features

    • updated generateExportEntry to expose node details (#1556) (05002f3)

    Bug Fixes

  • 6.8.1 - 2023-05-28

    6.8.1 (2023-05-28)

    Bug Fixes

    • use cause for original errors and warnings (#1526) (ae3d8ae)
from css-loader GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Upgrade css-loader to version 7.1.2 to resolve security vulnerabilities and adopt the latest major release

Bug Fixes:

  • Address multiple high- and medium-severity security issues via the updated css-loader release

Enhancements:

  • Bump css-loader from ^6.7.3 to ^7.1.2 (major version upgrade)

Snyk has created this PR to upgrade css-loader from 6.8.1 to 7.1.2.

See this package in npm:
css-loader

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/aa77fd79-7d27-4ab0-9d41-5dd117531784?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Jul 12, 2025

Reviewer's Guide

This PR upgrades the css-loader package from v6.8.1 to v7.1.2 by updating the devDependency in package.json (and regenerating the lockfile), addressing several security vulnerabilities and incorporating bug fixes and new features, while introducing potential breaking changes in loader defaults.

File-Level Changes

Change Details Files
Upgrade css-loader dependency
  • Bump css-loader version in devDependencies from ^6.8.1 to ^7.1.2
  • Regenerate lockfile to lock the new css-loader and its transitive dependencies
glances/outputs/static/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

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