Summary
Reduce initial bundle size by code-splitting PDF-heavy and workspace-heavy modules.
Why
Production builds already emit chunk-size warnings, which suggests the initial load path is doing more work than necessary.
Current evidence
npm run build reports large chunks after minification.- PDF rendering and advanced workspace features are not needed for every first paint.
Scope
- Identify candidate modules for dynamic import (for example:
react-pdf, quick flip overlay, workspace-heavy panes).
- Split code paths without degrading user-perceived responsiveness.
- Re-test import, reader, and quick flip flows after splitting.
Acceptance criteria
- Initial bundle cost is reduced measurably.
- The app still feels responsive when loading deferred modules.
- Build output no longer triggers avoidable large-chunk warnings, or warnings are clearly justified.
Out of scope
Summary
Reduce initial bundle size by code-splitting PDF-heavy and workspace-heavy modules.
Why
Production builds already emit chunk-size warnings, which suggests the initial load path is doing more work than necessary.
Current evidence
npm run buildreports large chunks after minification.Scope
react-pdf, quick flip overlay, workspace-heavy panes).Acceptance criteria
Out of scope