Template error: Missing module import for PrimeNG AutoComplete

Component Import Strategy for Bundle Optimization

In a low-traffic Angular application, reducing the initial JavaScript payload is a primary goal to minimize client-side load costs. PrimeNG supports granular, per-component imports to facilitate tree-shaking and reduce the final bundle size.

While importing only the necessary components (such as AutoCompleteModule) prevents the inclusion of unused library code, this approach increases the risk of template errors if a component is used without its corresponding module being declared in the standalone imports or the NgModule.

There is currently no documented standard for balancing the developer overhead of granular imports against the bundle size benefits for low-traffic scenarios. It remains unclear whether a shared internal PrimeNG module or individual component imports provide the optimal trade-off for build performance and maintenance.

• Does PrimeNG provide a recommended import granularity for maximizing tree-shaking in standalone Angular applications?
• What is the impact on initial load time when utilizing a shared PrimeNG wrapper module versus direct component imports?