[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
	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 is an automated security upgrade initiated by Snyk to resolve a critical vulnerability by updating the webpack dependency to a newer, more secure version. This change aims to enhance the project's security posture and ensure dependency integrity.

Highlights

• Security Vulnerability Fix: This pull request was automatically generated by Snyk to address a critical security vulnerability (SNYK-JS-FORMDATA-10841150) identified as 'Predictable Value Range from Previous Values'.
• Dependency Version Upgrade: The webpack dependency in fixtures/packaging/webpack/prod/package.json has been upgraded from version ^1.14.0 to ^2.2.0.

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 is currently in preview and 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 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, aims to resolve a security vulnerability by upgrading webpack from version 1.15.0 to 2.2.0.

While the dependency upgrade is necessary, it introduces breaking changes from webpack v1 to v2 that will cause the build to fail for the webpack-prod-fixture. The webpack configuration file needs to be updated to be compatible with v2.

Additionally, a similar webpack-dev-fixture exists in the repository which also uses the vulnerable version of webpack but has not been updated in this PR. To fully resolve the security issue and maintain consistency, it should be updated as well.

I've added detailed comments on the package.json change. Please address these issues to ensure the project remains buildable and secure.

[gemini-code-assist]

Upgrading webpack from v1 to v2 is a major version bump that introduces breaking changes. The current webpack configuration in fixtures/packaging/webpack/prod/config.js is not compatible with webpack v2 and will cause the build for this fixture to fail.

Specifically, the resolve.root option used in the config has been removed in webpack v2. It should be replaced with resolve.modules.

The configuration file needs to be updated for this dependency upgrade to work. For example:

// in fixtures/packaging/webpack/prod/config.js
resolve: {
  modules: [
    path.resolve('../../../../build/node_modules/'),
    'node_modules' // Also recommended to keep resolving from node_modules
  ],
},

Without this change, the yarn build script for this fixture will fail.

[gemini-code-assist]

This PR only upgrades the webpack dependency for the prod fixture. However, the dev fixture at fixtures/packaging/webpack/dev/package.json still uses the old, vulnerable version (webpack: "^1.14.0").

To fully address the security vulnerability and maintain consistency, the dev fixture's dependencies should also be upgraded. Note that its configuration file, fixtures/packaging/webpack/dev/config.js, will also require updates to be compatible with webpack v2.