[email protected]

Patch Changes

• #1624 e2b007f Thanks @SutuSebastian! - fix(wrapDefaultExport): handle complex multiline exports

[email protected]

Patch Changes

• #1621 c02a977 Thanks @SutuSebastian! - fix: Error: spawn npm ENOENT

[email protected]

Patch Changes

• #1615 50ae2ee Thanks @SutuSebastian! - fix(ui/cli/plugins): setup-plugin-bun also detect Bun.build

[email protected]

Patch Changes

• #1612 941a075 Thanks @SutuSebastian! - Fix nextjs plugin to work on all environments

  Changes

  • fix(ui): nextjs plugin to run properly on NODE_ENV environments: production, development and test
  • log file writes in dev

  Breaking changes

  withFlowbiteReact now always returns async configuration (see: Async Configuration) so make sure to wrap any other HOC (higher-order-functions) such as withContentlayer because most of them do not forward pass async config arguments (eg: phase, options)

  // ❌ not working
  export default withContentlayer(withFlowbiteReact(nextConfig));
  
  // ✅ working
  export default withFlowbiteReact(withContentlayer(nextConfig));

[email protected]

Patch Changes

• #1608 e1b5bb1 Thanks @SutuSebastian! - fix: (node:50743) [DEP0190] DeprecationWarning

[email protected]

Patch Changes

• #1607 a89a098 Thanks @SutuSebastian! - fix: Error: Cannot find module 'tailwindcss/plugin'

• #1605 262cde0 Thanks @SutuSebastian! - Search for <ThemeInit /> in the project and warn if it's not found instead of warning all the time

  Changes

  • during commands build and dev check files content for custom configuration and display a warning if <ThemeInit /> is not found
  • switch tests in src/cli and src/helpers from vitest -> bun:test

[email protected]

Patch Changes

• #1600 12d3290 Thanks @SutuSebastian! - fix(ui/cli/setup-init): nextjs warning

  Changes

  • rename config -> CONFIG export in .flowbite-react/init.(jsx|tsx)

[email protected]

Patch Changes

• #1596 ab26436 Thanks @SutuSebastian! - refactor(setup-init): relax checks on React imports due to IDE formatters removing it if not necessary

  • filter out import React from "react" from the AST when parsing current and new content

[email protected]

Patch Changes

• #1594 9017065 Thanks @SutuSebastian! - fix(compareNodes): support:

  - different quote styles
  - with and without semicolons
  - trailing commas in objects and arrays
  

  • add tests

[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).