[Snyk] Security upgrade @storybook/builder-vite from 0.0.0-use.local to 0.1.22

[q1blue]

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

Snyk changed the following file(s):

• code/frameworks/experimental-nextjs-vite/package.json

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.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	708

---

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 @q1blue, 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 automates a critical security upgrade for the @storybook/builder-vite dependency. It resolves a medium-severity vulnerability concerning resource allocation, ensuring the project's dependencies are secure and up-to-date by updating a single package version.

Highlights

• Security Upgrade: Upgraded the @storybook/builder-vite dependency from workspace:* to 0.1.22 in code/frameworks/experimental-nextjs-vite/package.json.
• Vulnerability Fixed: Addressed a medium-severity vulnerability (SNYK-JS-QS-15268416) related to 'Allocation of Resources Without Limits or Throttling', identified by Snyk with a score of 708.
• Automated Remediation: This pull request was automatically generated by Snyk to apply the necessary security fix.

Changelog

• code/frameworks/experimental-nextjs-vite/package.json
  • Updated the version of @storybook/builder-vite to 0.1.22.

Activity

• Snyk automatically created this pull request to fix a security vulnerability.
• The PR description notes that yarn.lock was not updated and advises manual intervention for users leveraging Yarn's zero-installs feature.

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 incorrectly replaces a workspace dependency with a fixed, outdated version. In a monorepo, internal packages should maintain their workspace linkage to ensure consistency and use the local source code. Pinning to 0.1.22 will break the build and is a significant downgrade from the current 8.3.0-beta.3 version.

[gemini-code-assist]

Changing the dependency from workspace:* to 0.1.22 is incorrect for this monorepo. This package should depend on the version of @storybook/builder-vite defined within the workspace (currently 8.3.0-beta.3). Pinning to an old version breaks the linkage and will cause build failures. Security vulnerabilities in transitive dependencies should be handled in the builder's own package.json or the root lockfile.

Suggested change

	"@storybook/builder-vite": "0.1.22",
	"@storybook/builder-vite": "workspace:*",