perf(component treeshaking): updated config and build files to treesh…

[wheresdiasd]

Each component can now OPTIONALLY be imported individually from the components path.

EXAMPLE:

import { Badge } from "flowbite-react/components/Badge";

function App() {
  return (
    <div className="w-10/12">
      <Badge>Test</Badge>
    </div>
  );
}

Components with old pattern:

import { Badge } from "flowbite-react";

function App() {
  return (
    <div className="w-10/12">
      <Badge>Test</Badge>
    </div>
  );
}

Will still work, but will still treeshake hell as well.

PS: This pr will not fix the themes treeshaking which seems to be more complex.

#1197

Keen to hear back from the maintainers.

FINAL BUILD RESULT with "/components":

FINAL BUILD RESULT w/out "/components":

[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	Jan 8, 2024 2:50am

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7461173) 99.54% compared to head (dd3df45) 97.36%.
Report is 185 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1218      +/-   ##
==========================================
- Coverage   99.54%   97.36%   -2.18%     
==========================================
  Files         163      214      +51     
  Lines        6621     9077    +2456     
  Branches      401      530     +129     
==========================================
+ Hits         6591     8838    +2247     
- Misses         30      239     +209     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[SutuSebastian]

Will be implemented in the next version of the monorepo -> next release

[antonio-ivanovski]

The approach is OK, think it solves partially the reported issue of #1197.

Will be implemented in the next version of the monorepo -> next release

@SutuSebastian is this fix you are mentioning part of 7.3? What version will the fix be in? Is there a PR of the fix you mentioned?

[SutuSebastian]

The approach is OK, think it solves partially the reported issue of #1197.

Will be implemented in the next version of the monorepo -> next release

@SutuSebastian is this fix you are mentioning part of 7.3? What version will the fix be in? Is there a PR of the fix you mentioned?

There is a PR on it, its #1264, almost done.

[SutuSebastian]

Fixed in #1264