Skip to content

Performance pitfall - imports not tree shaken #1197

@timthedev07

Description

@timthedev07
  • I have searched the Issues to see if this bug has already been reported
  • I have tested the latest version

Steps to reproduce

  1. Import a single component from any page in Next.js
  2. Use the Next.js bundle analyzer to open up the tree diagram
  3. Find the page used in step 1 and look for Flowbite react

Current behavior

All components are imported.

Expected behavior

Only the desired component should show up.

Context

截屏2023-12-23 01 41 58

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions