[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version
Summary
When a CRA project using Flowbite is used in a monorepo setup e.g. NPM workspaces, the flowbite-react and flowbite packages get hoisted to the top-level node_modules folder. While the build (via npm run build), works as expected, the resultant CSS artifacts don't contain all the CSS.
This is documented in the library but requires a deep understanding of the CRA configuration to figure this out.
I suggest that better warnings be emitted or a exception be thrown if the required directory is missing.
Summary
When a CRA project using Flowbite is used in a monorepo setup e.g. NPM workspaces, the
flowbite-react
andflowbite
packages get hoisted to the top-level node_modules folder. While the build (vianpm run build
), works as expected, the resultant CSS artifacts don't contain all the CSS.This is documented in the library but requires a deep understanding of the CRA configuration to figure this out.
I suggest that better warnings be emitted or a exception be thrown if the required directory is missing.
https://github.com/themesberg/flowbite-react/blob/83e5583d978d8938be69e4cf51fe10d67b2e68e4/packages/ui/src/tailwind.ts#L4-L32
Context
I was trying to use React + Flowbite + Tailwind (using CRA) in a package which is a part of a NPM monorepo