Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Minor Changes

• #1566 7b79b18 Thanks @SutuSebastian! - # Breaking changes

  • removed flowbite-react patch CLI command

  Changes

  • flowbite-react/.gitignore, flowbite-react/config.json self manages, regenerates and repairs
  • new generated file init.(jsx|tsx) in .flowbite-react/ directory that syncs up values from config.json that also are needed in React app runtime (similar to how a React context works)
    • synced on CLI commands: init, build, dev, register
  • If you have custom configuration in .flowbite-react/config.json (different dark/prefix/version values), you must render <ThemeInit /> at the root level of your app to sync runtime with node config values
    • notify users to include <ThemeInit /> at the root level if custom dark, prefix, or version values are detected in the configuration file
  • expose flowbite-react/store import path
  • check if flowbite-react is installed when npx flowbite-react@latest init
    • bump the version to latest if below 0.11.x
  • remove redundant { flag: "w" } in fs.writeFile
  • update dark-mode.md and prefix.md documentation to reflect the <ThemeInit /> changes
  • add Tailwind CSS version support in theme mode handling and fix dark theme toggle class in Tailwind CSS v4

  Migration Guide

  1. Remove flowbite-react patch from your package.json

     {
       "scripts": {
     -   "postinstall": "flowbite-react patch"
       }
     }

  2. Add <ThemeInit /> (import from .flowbite-react/init.(jsx|tsx)) at the root level of your app if you have custom configuration in .flowbite-react/config.json (different dark/prefix/version values).

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
flowbite-react	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 22, 2025 0:07am
flowbite-react-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 22, 2025 0:07am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.