[Snyk] Security upgrade webpack from 1.15.0 to 2.2.0

[saurabharch]

Snyk has created this PR to fix 1 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
	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 @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, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the webpack dependency. The primary goal is to remediate a critical vulnerability related to incorrect argument types. The change involves updating the webpack version in package.json, which is a substantial version bump and should be reviewed for potential compatibility issues.

Highlights

• Dependency Upgrade: The webpack dependency has been upgraded from version 1.15.0 to 2.2.0. This is a significant version jump and might introduce breaking changes, as indicated by Snyk's metadata.
• Security Fix: This upgrade specifically addresses a critical vulnerability identified as SNYK-JS-SHAJS-12089400, described as 'Function Call With Incorrect Argument Type', which had a high score of 848.

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 pull request, automatically generated by Snyk, upgrades webpack from version 1.15.0 to 2.2.0 to resolve a security vulnerability. While this is an important security update, it's a major version bump which introduces significant breaking changes. Your current Webpack configuration files (webpack.config.js and webpack.prod.config.js) are incompatible with Webpack 2 and will cause your build to fail. I've added a critical comment on the package.json change detailing the necessary updates you'll need to make to your configuration files before this PR can be merged.

[gemini-code-assist]

Upgrading Webpack from v1 to v2 is a major change that includes many breaking changes. Your current Webpack configuration files will not work with Webpack 2 and need to be updated. Without these changes, your build will fail.

Here are some of the required changes I've identified:

In both webpack.config.js and webpack.prod.config.js:

• resolve.extensions: The empty string '' is no longer needed for resolving extensionless files and should be removed from the array. In Webpack 2, you should not use an empty string.
• module.loaders: This has been renamed to module.rules.
• json-loader: This is no longer necessary as Webpack 2 handles JSON files by default. You can remove this loader.
• ExtractTextPlugin: The syntax for ExtractTextPlugin.extract has changed. The old string-based syntax is no longer valid. You'll need to migrate to the new object-based syntax. For example:

  ExtractTextPlugin.extract({
    fallback: 'style-loader',
    use: [
      { loader: 'css-loader', options: { sourceMap: true } },
      { loader: 'sass-loader', options: { sourceMap: true } }
    ]
  })

In webpack.config.js:

• module.preLoaders: This has been removed. You should merge its contents into module.rules and use the enforce: 'pre' property on the rule.

In webpack.prod.config.js:

• webpack.DefinePlugin: The current configuration for DefinePlugin overwrites the entire process.env object. It should be changed to only define process.env.NODE_ENV:

  new webpack.DefinePlugin({
    'process.env.NODE_ENV': JSON.stringify('production')
  })

I strongly recommend consulting the official Webpack v1 to v2 migration guide for a complete list of changes and detailed instructions.