Skip to content

Missing Bundle Splitting Causes Unnecessary Initial JavaScript Loading#336

Description

@Tushar15769

馃搶 Description

All registry components, icons, and supporting modules are loaded eagerly into the initial application bundle.

Current behavior:

All Lucide icons are imported at startup
Registry components are loaded eagerly
No React.lazy() implementation exists
No Suspense boundaries are present
Category-specific code is included in the initial bundle
No route-based code splitting exists

Because code splitting is not implemented, users download code that may never be used during a session.

As a result:

Initial bundle size increases
Application startup becomes slower
Time-to-interactive is negatively impacted
Network utilization is inefficient
Scalability decreases as more components are added

馃幆 Expected Behavior

Components should be loaded lazily
Route-based code splitting should be implemented
Unused code should not be downloaded initially
Suspense boundaries should handle loading states
Bundle size should remain optimized as the library grows

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions