[Snyk] Security upgrade gatsby from 2.32.13 to 4.22.0

[saurabharch]

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

Snyk changed the following file(s):

• examples/using-stylus/package.json

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 improve the project's security posture by upgrading a core dependency. The change specifically targets a critical vulnerability identified in the gatsby framework within one of the example projects, ensuring the application uses a more secure and up-to-date version.

Highlights

• Security Vulnerability Remediation: This pull request automatically addresses a critical security vulnerability (SNYK-JS-FORMDATA-10841150: Predictable Value Range from Previous Values) by upgrading a key dependency.
• Dependency Version Update: The gatsby dependency in examples/using-stylus/package.json has been updated from ^2.0.0 to ^4.22.0. This is a significant major version upgrade.
• Automated Pull Request: This pull request was automatically generated by Snyk to propose a fix for an identified vulnerability.

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 upgrades Gatsby from v2 to v4 to fix a security vulnerability. However, this is a major version upgrade that introduces breaking changes. The current change only updates the gatsby package, which will likely break the build. The comment explains that all related Gatsby plugins and React must also be upgraded, and that the deprecated gatsby-plugin-offline must be removed to make the example work with Gatsby v4.

[gemini-code-assist]

Upgrading Gatsby from v2 to v4 is a major change that introduces significant breaking changes. Simply updating the gatsby package version is insufficient and will likely break the build for this example.

To ensure compatibility with Gatsby v4, you need to update other related packages as well:

• Gatsby Plugins: All gatsby-plugin-* packages should be upgraded to versions compatible with Gatsby v4. For [email protected], the corresponding plugins should also be at ^4.22.0.
• React: Gatsby v4 requires React 17 or 18. The current version ^16.4.2 is incompatible. You should upgrade react and react-dom to ^18.0.0.
• gatsby-plugin-offline: This plugin is deprecated and not compatible with Gatsby v4. It should be removed from the dependencies. The PWA functionality it provides can be achieved using gatsby-plugin-manifest. This will also require changes in gatsby-config.js.