[Snyk] Security upgrade webpack-dev-server from 3.2.1 to 4.7.3

[saurabharch]

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

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Interpretation Conflict SNYK-JS-NODEFORGE-14114940	751
	Uncontrolled Recursion SNYK-JS-NODEFORGE-14125745	721
	Integer Overflow or Wraparound SNYK-JS-NODEFORGE-14125097	601

---

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 @saurabharch, 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 enhances the project's security by updating the webpack-dev-server dependency to a more secure version. The update specifically targets and resolves three identified vulnerabilities, ranging from critical to medium severity, ensuring a safer development environment.

Highlights

• Security Upgrade: Upgraded the webpack-dev-server dependency from version "3.2.1" to "4.7.3" to address multiple security vulnerabilities.
• Vulnerability Fixes: This upgrade resolves three specific vulnerabilities: a critical 'Interpretation Conflict' (SNYK-JS-NODEFORGE-14114940), a high severity 'Uncontrolled Recursion' (SNYK-JS-NODEFORGE-14125745), and a medium severity 'Integer Overflow or Wraparound' (SNYK-JS-NODEFORGE-14125097).
• Automated Remediation: This pull request was automatically generated by Snyk to apply the necessary security fixes.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 pull request, automatically generated by Snyk, upgrades webpack-dev-server from version 3.2.1 to 4.7.3 to fix several security vulnerabilities. While the security upgrade is important, this is a major version bump that introduces significant breaking changes. As it stands, the PR will break the development environment because it does not account for the new API and configuration requirements of webpack-dev-server v4, nor does it upgrade the webpack dependency which is now incompatible. My review includes a critical comment detailing the necessary changes to make this upgrade work.

[gemini-code-assist]

Upgrading webpack-dev-server from v3 to v4 is a major change that introduces several breaking changes. Merging this PR as-is will break the development server because it requires code and configuration updates that are not included here.

Here are the critical issues that need to be addressed:

1. webpack Dependency: webpack-dev-server v4 requires webpack version 4.37.0 or newer. This project uses version 4.29.6, which is incompatible. You'll need to upgrade the webpack dependency in this file.

2. WebpackDevServer API Change: The constructor signature has changed. In scripts/start.js (line 107), the call new WebpackDevServer(compiler, serverConfig) needs to be changed to new WebpackDevServer(serverConfig, compiler).

3. Configuration Changes: The configuration file config/webpackDevServer.config.js uses several options that have been removed or renamed in v4. These will cause the server to fail to start. Here's a list of required changes based on your current configuration:

   • disableHostCheck: Removed. Use allowedHosts.
   • clientLogLevel: Removed. Use client: { logging: 'none' }.
   • contentBase: Removed. Use static: { directory: ... }.
   • watchContentBase: Removed. Use static: { watch: true }.
   • publicPath: Moved to devMiddleware: { publicPath: '/' }.
   • quiet: Removed. Use client: { logging: 'none' } or similar.
   • watchOptions: Removed. Use watchFiles.
   • overlay: Moved to client: { overlay: false }.
   • public: Removed. Use allowedHosts.
   • before(): Removed. Use onBeforeSetupMiddleware().

Given the extent of these breaking changes, I recommend either expanding this PR to include all the necessary fixes or creating a new manual PR to handle the upgrade comprehensively.