You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the Issues to see if this bug has already been reported
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.
flowbite-react/packages/ui/src/tailwind.ts
Lines 4 to 32 in 83e5583
Context
I was trying to use React + Flowbite + Tailwind (using CRA) in a package which is a part of a NPM monorepo
The text was updated successfully, but these errors were encountered: