Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsAn Angular injection context is a synchronous execution frame in which Angular makes an injector available to inject(). It is available during DI-managed construction, including field initializers, and in certain factories and Angular-run functional APIs. It does not automatically extend to later methods, lifecycle hooks, or asynchronous callbacks.
What is an injection context in Angular?
An injection context is where Angular has made a current injector available to the code running at that moment. Calling inject(Token) in that frame asks the injector to resolve the token. This is about where and when the code executes, not simply whether it belongs to a class that uses dependency injection.
As an Amazon Associate I earn from qualifying purchases.
Angular documents these common valid contexts:
- A constructor of a class instantiated by Angular’s dependency-injection system.
- A field initializer of a class instantiated by that system.
- A provider or injectable factory configured with
useFactory. - An
InjectionTokenfactory. - A synchronous stack frame called while an injection context is already active, including Angular-executed functional APIs such as route guards.
See Angular’s injection context guide and inject() API reference for the documented contexts.
Why does inject() fail in ngOnInit or a method?
Angular runs a DI-managed class’s constructor and field initializers while establishing its dependencies. An ordinary method such as onClick() runs later, and lifecycle hooks such as ngOnInit run after construction. Neither becomes an injection context just because it belongs to an injected component or service.
#1 Best Overall
import { Component, inject } from '@angular/core';
import { DataService } from './data.service';
@Component({ selector: 'app-example', template: '' })
export class ExampleComponent {
private readonly dataService = inject(DataService); // valid field initializer
ngOnInit() {
// inject(DataService); // NG0203: this runs after construction
this.dataService.load();
}
}Angular reports the invalid call as NG0203: inject() must be called from an injection context. Its NG0203 error reference advises checking where the failing call occurs; the DI troubleshooting guide covers ways to handle later lookups.
Can I use inject() after await?
No. The injection context is synchronous. It is not carried into a promise continuation, timer, event callback, or code after await. runInInjectionContext also makes the injector current only while its callback’s synchronous stack frame runs; it cannot preserve the context for asynchronous work started inside that callback. Angular explains this boundary in its runInInjectionContext API reference.
runInInjectionContext(injector, () => {
const service = inject(DataService); // valid here
setTimeout(() => {
// inject(DataService) is not valid here
service.load(); // use the captured reference instead
});
});How to fix NG0203
Capture the dependency during construction
For component, directive, or service code that needs a dependency later, inject it in a constructor or field initializer and retain the reference. Use that reference from methods, lifecycle hooks, and callbacks.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use an existing injector for a later lookup
If you need a one-off lookup in later code and already have an Injector, use Injector.get(Token). This performs retrieval through that injector without requiring the later method itself to be an injection context.
Rank #3
Wrap a synchronous callback when it must call inject()
When an external synchronous callback specifically needs to invoke inject(), call it through runInInjectionContext(injector, callback), using an injector you already have. Any dependency needed by asynchronous work must still be captured before the callback returns.
In tests, use TestBed’s context helper
Angular’s NG0203 documentation identifies TestBed.runInInjectionContext for test code that must call inject() in a context supplied by TestBed. See the error reference for details.
An injection context does not guarantee a provider exists
Context and resolution are separate questions. A current injector makes inject() eligible to run, but that injector must still be able to resolve the requested token. If the error is NG0203, investigate where the call runs. If a context is active but a token cannot be resolved, investigate provider registration and scope instead. Angular describes the EnvironmentInjector and ElementInjector hierarchies and how provider configuration affects resolution.
Make reusable helpers fail more clearly
A helper that calls inject() can use assertInInjectionContext(helperFunction) to check its precondition and produce a more useful error associated with that helper. The assertion does not create an injection context; callers must still invoke the helper from a valid one. Angular documents this in its injection context guide.
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.
