Skip to content

[Snyk] Security upgrade clean-webpack-plugin from 0.1.19 to 2.0.0#151

Open
grootjans wants to merge 1 commit into
masterfrom
snyk-fix-ff0895832711536449b3d006f90b84d1
Open

[Snyk] Security upgrade clean-webpack-plugin from 0.1.19 to 2.0.0#151
grootjans wants to merge 1 commit into
masterfrom
snyk-fix-ff0895832711536449b3d006f90b84d1

Conversation

@grootjans

Copy link
Copy Markdown

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

@grootjans

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade from v0.1.19 to v2.0.0 that introduces significant breaking changes in how the plugin is configured.

Key Breaking Changes:

  • Configuration Overhaul: All configuration options from versions prior to v2.0.0 have been removed and replaced. Options such as paths, exclude, root, watch, and beforeEmit are no longer valid.
  • New Default Behavior: By default, the plugin now cleans the entire directory specified in webpack's output.path without needing any configuration.
  • New Options: For custom cleaning patterns, you must now use new options like cleanOnceBeforeBuildPatterns and cleanAfterEveryBuildPatterns.

Recommendation:
Your webpack.config.js file must be updated. Remove the old clean-webpack-plugin options and instantiate the plugin with no arguments for the default behavior, or use the new cleanOnceBeforeBuildPatterns option for custom paths.

Example (Old v0.1.x):
new CleanWebpackPlugin(['dist'], { root: __dirname })

Example (New v2.0.0):
new CleanWebpackPlugin()

Source: GitHub Release Notes and 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