chore(web): remove redundant optimizePackageImports config

[cxhello]

Summary

Remove the explicit @heroicons/react configuration from optimizePackageImports as it is already included in Next.js default configuration.

Before:

experimental: {
  optimizePackageImports: [
    '@heroicons/react',
  ],
},

After:
Configuration removed (using Next.js defaults).

Screenshots

N/A (config change only, no UI changes)

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

References

• Next.js optimizePackageImports defaults

Fixes #31255

[gemini-code-assist]

Summary of Changes

Hello @cxhello, 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 streamlines the Next.js configuration by eliminating a redundant entry for @heroicons/react within the optimizePackageImports experimental setting. By relying on Next.js's built-in default optimizations, the change simplifies the project's configuration file without altering the intended behavior, ensuring efficient package importing for Heroicons.

Highlights

• Configuration Simplification: Removed the explicit @heroicons/react entry from the optimizePackageImports configuration in web/next.config.js.
• Leveraging Next.js Defaults: The project now relies on Next.js's default optimizePackageImports settings, which already include @heroicons/react, making the explicit configuration redundant.

🧠 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.

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 correctly removes a redundant optimizePackageImports configuration for @heroicons/react from the next.config.js file. As noted in the pull request description, this package is already included in Next.js's default optimizations. This change improves code maintainability by removing unnecessary configuration. The change is sound and I found no issues with it.