[Snyk] Security upgrade node-polyfill-webpack-plugin from 2.0.1 to 4.1.0

[paaschdigital]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• components/dash-core-components/package.json
• components/dash-core-components/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Function Call With Incorrect Argument Type SNYK-JS-CIPHERBASE-12084814	848
	Function Call With Incorrect Argument Type SNYK-JS-SHAJS-12089400	848

---

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.

[gemini-code-assist]

Summary of Changes

Hello @paaschdigital, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, upgrades the node-polyfill-webpack-plugin dependency to address two critical security vulnerabilities. The update ensures the project's dependencies are more secure by bringing this package up to its latest stable version.

Highlights

• Dependency Upgrade: Upgraded node-polyfill-webpack-plugin from version 2.0.1 to 4.1.0.
• Security Fixes: Addresses two critical vulnerabilities, SNYK-JS-CIPHERBASE-12084814 and SNYK-JS-SHAJS-12089400, identified by Snyk.
• Configuration Updates: Modified components/dash-core-components/package.json and components/dash-core-components/package-lock.json to reflect the dependency version change.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR from Snyk upgrades node-polyfill-webpack-plugin from v2.0.1 to v4.1.0 to fix two critical vulnerabilities. While this is an important security update, it's a major version bump flagged as a breaking change, which introduces risks. Furthermore, the update is only applied to the dash-core-components package. The dash-renderer package also appears to use this dependency (in dash/dash-renderer/webpack.test.config.js) but is not updated in this PR. To fully address the security vulnerability across the project and maintain dependency consistency, node-polyfill-webpack-plugin should be updated in dash-renderer as well.

[gemini-code-assist]

This major version upgrade from v2 to v4 introduces a high risk of breaking changes, as noted by Snyk. The current usage in components/dash-core-components/webpack.config.js is a simple instantiation (new NodePolyfillPlugin()), which may be incompatible with the new version or exhibit different behavior, potentially causing build failures.