[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/dev/package.json
• fixtures/packaging/webpack/dev/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
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	863

---

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, focuses on improving the project's security by performing a critical dependency upgrade. The primary goal is to remediate a known vulnerability by bumping the webpack package to a more secure major version, ensuring the project benefits from the latest security patches and improvements.

Highlights

• Security Upgrade: I've upgraded the webpack dependency from version 1.15.0 (specifically ^1.14.0 in package.json) to 2.2.0 (specifically ^2.2.0 in package.json). This update is crucial for addressing a critical security vulnerability, SNYK-JS-FORMDATA-10841150, identified by Snyk.
• Dependency Management: The package.json file has been updated to reflect the new webpack version, and the yarn.lock file has been regenerated to ensure dependency consistency and lock the new dependency tree.

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 or fill out our survey to provide feedback.

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 to 2 in a test fixture to resolve a security vulnerability. While the dependency upgrade is correct, it's a major version change that introduces breaking changes. My review points out that the existing webpack configuration for this fixture is incompatible with webpack v2 and will cause the build to fail. The PR needs to be amended to include the necessary configuration migration before it can be merged.

[gemini-code-assist]

Upgrading webpack from v1 to v2 is a major version bump that introduces breaking changes. This will likely break the build for this fixture.

The associated webpack configuration file, fixtures/packaging/webpack/dev/config.js, uses the resolve.root option, which was removed in webpack v2. The build script in this package.json will fail when webpack is executed with this configuration.

To resolve this, the config.js file needs to be updated for webpack v2. Specifically, resolve.root should be replaced with resolve.modules.

For example:
Webpack v1 (config.js)

resolve: {
  root: path.resolve('../../../../build/node_modules/'),
}

Webpack v2 (required change in config.js)

resolve: {
  modules: [
    path.resolve('../../../../build/node_modules/'),
    'node_modules', // Also recommended to add 'node_modules'
  ],
}

This PR should be updated to include the necessary configuration changes to ensure the fixture remains buildable.