Template error: Missing module import for PrimeNG AutoComplete

Direct Component Imports for Tree-Shaking

To maximize tree-shaking in standalone Angular applications, PrimeNG recommends importing only the specific modules required for your components. For the AutoComplete component, you should import AutoCompleteModule directly from its specific entry point.

import { AutoCompleteModule } from 'primeng/autocomplete';

In a standalone component, add this to your imports array:

@Component({
  standalone: true,
  imports: [AutoCompleteModule, ...],
  template: `<p-autoComplete [(ngModel)]="value" [suggestions]="suggestions" (completeMethod)="search"></p-autoComplete>`
})
export class MyComponent { }

Analysis: Direct Imports vs. Shared Wrapper Modules

The impact on initial load time is directly tied to the bundle size. Because PrimeNG is shipped as ES2015 modules with sideEffects: false, the Angular compiler (Ivy) can effectively remove unused code during the production build process.

Import Strategy	Tree-Shaking Impact	Bundle Size Effect
Direct Component Import	Optimal	Minimum; only the specific component and its dependencies are included.
Shared Wrapper (Selective)	High	Negligible difference if the wrapper only re-exports used modules.
Shared Wrapper (Bulk)	Poor	Increased; importing a large library bundle can bloat the main JS payload.

Using a shared wrapper that imports the entire PrimeNG library defeats tree-shaking, potentially increasing the main bundle size by several hundred kilobytes. Direct imports ensure that only the AutoComplete logic is shipped to the client.

Verification Steps

To quantify the impact on your specific application, follow these steps:

1. Run a production build: ng build --configuration production.
2. Analyze the resulting bundles using a tool like source-map-explorer or webpack-bundle-analyzer.
3. Compare the size of the main.js bundle when using direct imports versus a shared wrapper.

Diagnostic Detail: Are you currently using a shared module that exports the PrimeNG modules, or are you importing the entire PrimeNG` library from a single index file?