[Snyk] Security upgrade webpack from 1.15.0 to 2.2.0

[saurabharch]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• fixtures/packaging/webpack/prod/package.json
• fixtures/packaging/webpack/prod/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	828

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[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 mitigate a high-severity vulnerability related to resource allocation without limits, ensuring the project utilizes a more secure and updated version of this critical build tool.

Highlights

• Security Upgrade: Upgrades the webpack dependency from version ^1.14.0 to ^2.2.0 to address a critical security vulnerability.
• Vulnerability Fixed: Resolves the high-severity vulnerability 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-QS-14724253), which was identified with a score of 828.
• Dependency File Updates: Modifies fixtures/packaging/webpack/prod/package.json and fixtures/packaging/webpack/prod/yarn.lock to reflect the updated webpack version.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 from ^1.14.0 to ^2.2.0 in the webpack/prod fixture to resolve a security vulnerability. While this is a necessary security update, it introduces a breaking change.

The upgrade is a major version bump from Webpack 1.x to 2.x, which has breaking changes in its configuration. The existing fixtures/packaging/webpack/prod/config.js file uses Webpack 1 syntax and will cause the build to fail with the updated dependency. I've left a specific comment detailing the required changes in the configuration file.

Additionally, I've noticed that fixtures/packaging/webpack/dev/package.json also uses a vulnerable version of webpack (^1.14.0) but was not updated in this PR. It would be best to update this dependency as well to ensure all fixtures are secure and consistent.

[gemini-code-assist]

Upgrading webpack from version 1.x to 2.x is a major change that includes several breaking changes. The associated webpack configuration file, fixtures/packaging/webpack/prod/config.js, is written for Webpack 1 and will not work with Webpack 2, causing the build to fail.

Specifically, the resolve.root option used in config.js has been deprecated in Webpack 2. It should be replaced with resolve.modules.

To fix the build, you'll need to update config.js as well. For example:

// In fixtures/packaging/webpack/prod/config.js
...
  resolve: {
    modules: [
      path.resolve('../../../../build/node_modules/'),
      'node_modules',
    ],
  },
...

Since this is an automated PR, this was likely missed. Please apply this change to ensure the fixture's build process is not broken.