Recommended Free Tools
NG8113 means an entry in a component’s imports array is not used by that component’s template. The usual fix is to remove the unused entry from the component metadata and, if no longer needed elsewhere, remove its TypeScript import too. Angular also lets you suppress this diagnostic through angularCompilerOptions, but that leaves the entry in place.
What NG8113 checks
NG8113 is Angular’s extended diagnostic named unusedStandaloneImports. It reports a component-level import that the component’s template does not use. The imports property in a component’s metadata makes directives, components, and pipes available to that template; standalone components can also include existing NgModules. The check concerns entries in this component-level list, not every TypeScript import in the file. See Angular’s NG8113 documentation and Component API.
As an Amazon Associate I earn from qualifying purchases.
For example, if a component’s metadata lists both UsedDirective and UnusedPipe, but its template uses only UsedDirective, NG8113 identifies UnusedPipe as unused. Angular’s documented fix is to remove that entry. The diagnostic page says unused imports “add unnecessary noise to your code and can increase your compilation time.” It gives no project-specific measurement, so this is a qualitative rationale, not a promise of a particular build-time or bundle-size improvement.
How to fix NG8113
- Locate the component. Find the
@Componentmetadata containing the reportedimportsarray. - Check the template. Look for actual use of each listed component, directive, and pipe in the inline template or the file named by
templateUrl. - Remove the unused entry. Delete the symbol from the component’s
importsarray. If its TypeScript import statement is no longer referenced elsewhere in the file, remove that too. - Run your normal compiler check. Rebuild or run the project’s usual Angular compiler check and confirm that NG8113 is gone.
If the symbol appears to be needed, verify that you are checking the template belonging to the component whose metadata contains the array. The diagnostic is about template use by that component; an import being used in another component does not make it used here.
#1 Best Overall
How to disable or change the NG8113 warning
Angular extended diagnostics are warnings by default. You can set an individual check to warning, error, or suppress. To stop Angular from emitting NG8113, add or update this configuration in the project’s tsconfig:
{
"angularCompilerOptions": {
"extendedDiagnostics": {
"checks": {
"unusedStandaloneImports": "suppress"
}
}
}
}Use error instead if you want unused standalone imports to fail compilation; warning keeps the diagnostic non-blocking. Angular documents these options in its extended diagnostics configuration and the NG8113 entry. Suppression changes whether the compiler reports the issue; it does not remove the unused metadata entry.
How CommonModule relates to NG8113
A standalone component can import individual directives and pipes, or an NgModule such as CommonModule. Angular’s CommonModule-to-standalone migration shows replacing a component-level CommonModule entry with the minimal imports used by its template, such as AsyncPipe, JsonPipe, and NgIf.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThat migration and NG8113 are related but distinct. The migration helps narrow a broad module import to specific standalone dependencies; NG8113 checks whether an entry in the component’s imports list is used by that template. Angular recommends standalone components for new code, while its migration guidance also covers existing NgModule-based applications. See Angular’s NgModules guide.
Rank #3
Version and tooling notes
Angular’s official documentation accessed on October 7, 2026, does not state the minimum Angular version that introduced NG8113. If version compatibility matters, check the documentation matching the Angular version installed in your project rather than assuming a version boundary.
Angular’s roadmap marks its broader initiative to streamline standalone imports with the Language Service as completed in Q4 2024. That roadmap item is not a claim that NG8113 automatically edits source files; the documented resolution is to remove the unused import yourself.
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.
