PrimeNG Component Imports: Unresolved Primeicons Tree‑Shaking Behavior
Goal The objective is to reduce the production bundle size for a low‑traffic Angular application that only uses a handful of PrimeNG components (e.g., ButtonModule , MenuModule ). By importing components via ES module entry points (v13+), Angular’s build optimizer can tree‑shake unused PrimeNG code. However, the peer dependency primeicons remains in the bund
angular