iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
NG8113 is Angular’s unusedStandaloneImports diagnostic. It means a component lists a directive, component, pipe, or NgModule in its imports array that its template does not use. The usual fix is to remove that entry from the component metadata and, if it is no longer needed elsewhere in the file, remove its TypeScript import too.
What NG8113 checks
A component’s imports metadata specifies which directives, components, and pipes are available to its template. A standalone component can also list NgModules there. NG8113 checks the entries in that component-level array for use in that component’s template; it does not mean that every TypeScript import in the file is unused.
For example, if a component imports UsedDirective and UnusedPipe in its metadata, but only uses UsedDirective in the template, Angular’s documented fix is to keep the directive and remove the pipe. Angular explains that unused imports “add unnecessary noise to your code and can increase your compilation time.” That is a qualitative rationale, not a quantified performance guarantee. Angular’s NG8113 documentation does not provide a project-specific speed or bundle-size estimate.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsHow to fix NG8113
-
Locate the
@Componentwhose metadata contains the reportedimportsarray.#1 Best Overall
-
Inspect the component’s template for each listed symbol. Check the inline template in the TypeScript file or the file referenced by
templateUrl. -
Remove the symbol that the template does not use from the component’s
importsarray. -
Remove its TypeScript import statement if the symbol is no longer referenced elsewhere in that file. Keep the TypeScript import if other code in the file still uses it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Run the project’s usual Angular compiler or build check and confirm NG8113 is gone.
The key distinction is between the component metadata and the TypeScript import declaration: NG8113 concerns the former. Removing an entry from metadata may leave a TypeScript import that should also be cleaned up, but only if it has no other use.
How to suppress or change the diagnostic
Angular extended diagnostics are warnings by default. You can configure an individual check as a warning, an error, or suppressed; an error fails compilation, while suppression prevents the diagnostic from being emitted. To suppress NG8113, add this to the project’s TypeScript configuration:
{
"angularCompilerOptions": {
"extendedDiagnostics": {
"checks": {
"unusedStandaloneImports": "suppress"
}
}
}
}Use the configuration file that applies to the Angular project’s compilation. The Angular extended diagnostics guide describes the available severity settings. Suppression keeps the compiler quiet but leaves the unused entry in place; removing a genuinely unused import keeps component metadata aligned with template use.
NG8113 and CommonModule
A standalone component may import individual directives and pipes, or import an NgModule such as CommonModule. Angular’s CommonModule-to-standalone migration shows replacing CommonModule with the smaller set of standalone imports required by a template, such as AsyncPipe, JsonPipe, and NgIf.
That migration and NG8113 are related, but they are not the same operation. NG8113 reports an entry that the component template does not use; the migration changes how dependencies are imported. Angular recommends standalone components for new code, while its NgModules documentation continues to cover existing NgModule-based applications.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Version considerations
Angular’s documentation accessed on October 7, 2026, does not specify the minimum Angular version that introduced NG8113. If compatibility matters, consult the documentation matching the Angular version installed in your project rather than assuming a version boundary.
The Angular roadmap says the broader initiative to streamline standalone imports with the Language Service was completed in Q4 2024. That tooling milestone is background context; it does not mean NG8113 automatically edits source files. Angular’s roadmap describes the initiative.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
