Why should you care?

ERP modules unused by most users should not block first paint.

See it live — copy this example

Paste into your MeanVerse project (Angular + Express + MongoDB), then run with ng serve / node / mongosh as noted.

export const routes: Routes = [
  {
    path: 'banking',
    loadChildren: () => import('./features/banking/banking.routes').then(m => m.BANKING_ROUTES)
  },
  {
    path: 'healthcare',
    loadComponent: () => import('./features/healthcare/patient-portal.component')
      .then(m => m.PatientPortalComponent)
  }
];
// banking.routes.ts exports BANKING_ROUTES with child paths

What happened?

• loadChildren pulls separate JS chunk on first /banking visit.
• loadComponent lazy-loads single standalone component.
• Users who never open healthcare never download it.

Practice next

1. Split MeanVerse by domain feature routes.
2. Verify separate chunks in dist/ after build.
3. Preload strategy optional for likely next routes.
4. Add withPreloading(PreloadAllModules) for admin users.
5. Measure LCP before and after lazy split.

Remember

Lazy routes defer JS download. loadComponent for standalone features. Critical path stays in main bundle.

Multi-product shell

MeanVerse users enable only SaaS module; banking chunk never loads.

Outcome: Initial bundle drops 40%; login faster on mobile.