chore(web): upgrade vite-plus and related packages to 0.1.13

[fengmk2]

• vite-plus: 0.1.12 → 0.1.13
• @voidzero-dev/vite-plus-core: 0.1.12 → 0.1.13
• @voidzero-dev/vite-plus-test: 0.1.12 → 0.1.13
• @storybook/nextjs-vite: 10.3.0 → 10.3.1

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello, 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 focuses on maintaining the project's frontend dependencies by upgrading vite-plus and its associated core and test packages to their latest patch version. Additionally, it includes a minor version bump for @storybook/nextjs-vite and propagates these changes throughout the dependency lockfile, ensuring compatibility and incorporating any bug fixes or minor enhancements from these updated libraries.

Highlights

• Dependency Upgrades: Upgraded vite-plus, @voidzero-dev/vite-plus-core, and @voidzero-dev/vite-plus-test from version 0.1.12 to 0.1.13.
• Storybook Package Updates: Updated @storybook/nextjs-vite from 10.3.0 to 10.3.1, along with corresponding updates to other Storybook-related packages and their peer dependencies in the lockfile.
• Internal Dependency Bumps: Several internal dependencies within the pnpm-lock.yaml were updated, including @oxc-project/runtime, @oxc-project/types, @oxfmt/* bindings, @oxlint-tsgolint/* bindings, and @oxlint/* bindings, reflecting minor version increments.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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 vite-plus and related packages to version 0.1.13, and @storybook/nextjs-vite to 10.3.1. The changes are consistent with the PR description. However, I've identified a potential peer dependency issue with the Storybook package updates. While @storybook/nextjs-vite is updated, other Storybook packages are not, which could lead to conflicts. Please see the specific comment for details.

[gemini-code-assist]

You've updated @storybook/nextjs-vite to 10.3.1, but other @storybook/* packages remain at 10.3.0. The new version of @storybook/nextjs-vite has a peer dependency on storybook@^10.3.1, which is not met by the currently installed version 10.3.0. This can cause peer dependency conflicts and potential issues. It's recommended to update all related @storybook/* packages to the same version to ensure compatibility.

For example:

    "@storybook/addon-docs": "10.3.1",
    "@storybook/addon-links": "10.3.1",
    "@storybook/addon-onboarding": "10.3.1",
    "@storybook/addon-themes": "10.3.1",
    "@storybook/nextjs-vite": "10.3.1",
    "@storybook/react": "10.3.1",
    ...
    "eslint-plugin-storybook": "10.3.1",
    ...
    "storybook": "10.3.1"