[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/web-components-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
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	210

---

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 @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, automatically generated by Snyk, aims to resolve a medium-severity security vulnerability by upgrading the @storybook/builder-vite dependency. While the package.json has been updated, the yarn.lock file requires manual synchronization to complete the fix and ensure consistent dependency resolution.

Highlights

• Security Fix: This pull request addresses a medium-severity vulnerability (SNYK-JS-TAR-15038581) identified as 'Improper Handling of Unicode Encoding'.
• Dependency Upgrade: The @storybook/builder-vite package has been upgraded from 0.0.0-use.local to version 0.1.22 in code/frameworks/web-components-vite/package.json.
• Automated Generation: This PR was automatically created by Snyk to provide a security fix for the identified vulnerability.
• Manual Intervention Required: The yarn.lock file failed to update automatically and requires manual synchronization before the pull request can be merged.

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, automatically generated by Snyk, aims to fix a security vulnerability by upgrading @storybook/builder-vite. However, the proposed change from "workspace:*" to a pinned, old version "0.1.22" is incorrect for this monorepo setup. It breaks the workspace linkage and introduces a massive version downgrade, which will almost certainly break the package. Additionally, the yarn.lock file was not updated, leading to an inconsistent state. I've left a critical comment suggesting to revert this change and address the underlying vulnerability through other means, such as using yarn resolutions.

[gemini-code-assist]

This change incorrectly replaces the yarn workspace dependency workspace:* with a pinned, and very old, version 0.1.22. This will likely break the build and the functionality of this package for several reasons:

1. Breaks Monorepo Link: It removes the link to the local @storybook/builder-vite package within the monorepo, which is currently at version 8.3.0-beta.3. Instead, it will fetch version 0.1.22 from the registry.
2. Major Version Downgrade: This is a significant downgrade from the version used in this workspace (8.3.0-beta.3) to 0.1.22. Such a large version jump backwards is almost certain to introduce breaking changes and incompatibilities.
3. Inconsistent Dependencies: The PR description notes that yarn.lock failed to update. This means the dependency tree is inconsistent and will cause issues.

While the intent is to fix a security vulnerability, this approach is incorrect and will likely cause more harm. The change should be reverted. The vulnerability in the tar package should be addressed differently, perhaps by updating the direct dependency that uses the vulnerable tar version, or by using resolutions in package.json to force a secure version of tar.

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