[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-alias/prod/package.json
• fixtures/packaging/webpack-alias/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, automatically generated by Snyk, aims to enhance the project's security posture by performing a significant upgrade of the webpack dependency from version 1 to version 2. The primary goal is to remediate a critical vulnerability identified in the older webpack version, ensuring the project uses more secure and up-to-date dependencies.

Highlights

• Major Version Upgrade: This pull request automatically upgrades the webpack dependency from ^1.14.0 to ^2.2.0. This is a significant jump from webpack major version 1 to major version 2, which Snyk notes as a potentially breaking change.
• Critical Vulnerability Fix: The primary purpose of this upgrade is to remediate a critical security vulnerability identified as SNYK-JS-FORMDATA-10841150. This vulnerability, described as 'Predictable Value Range from Previous Values,' has a high severity score of 863.
• Dependency File Updates: The changes involve updating fixtures/packaging/webpack-alias/prod/package.json to reflect the new webpack version and fixtures/packaging/webpack-alias/prod/yarn.lock to ensure consistency across the dependency tree after the upgrade.

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 ^1.14.0 to ^2.2.0 in a test fixture to resolve a security vulnerability. While the dependency upgrade is important, it introduces a breaking change. The Webpack configuration file for this fixture is incompatible with Webpack 2, which will cause the build to fail. I've left a comment detailing the required changes to the configuration file to ensure the fixture remains buildable after this upgrade.

[gemini-code-assist]

Upgrading webpack from v1 to v2 is a major version bump that introduces significant breaking changes. The current Webpack configuration for this fixture is not compatible with v2 and will cause the build script to fail.

The associated configuration file, fixtures/packaging/webpack-alias/prod/config.js, uses resolve.root, which was removed in Webpack 2. This option needs to be migrated to resolve.modules for the build to work.

Here's an example of how config.js should be updated:

  resolve: {
    modules: [path.resolve('../../../../build/node_modules'), 'node_modules'],
    alias: {
      // ...
    },
  },

While this upgrade is necessary for security, the configuration must be updated simultaneously to prevent breaking the build process for this fixture. You can find more information in the official Webpack migration guide.