Angular报错StaticInjectorError(AppModule)[options]排查求助

I’ve run into this exact vague injector error before—when Angular only shows [options] instead of a clear service/module name, it usually means the injection token is either custom, from a third-party library, or got mangled during minification. Let’s break down how to track this down:

• First, hunt down where Options is being injected
  Angular doesn’t have a built-in Options injection token by default, so this is definitely something custom or from a dependency. Search your entire codebase for:

  • @Inject(Options) (note the capitalization—case matters!)
  • Constructor parameters typed as Options (e.g., constructor(private options: Options))
    This will tell you which component/service is requesting this unprovided dependency.

• Check third-party libraries for missing setup
  If you’re using UI component libraries (like NgZorro, PrimeNG, or Angular Material) or other utilities, some components require specific Options providers or module imports. For example:

  • A date picker component might need a DatePickerOptions provider that you forgot to add to your module’s providers array.
  • Double-check the docs for any recently added libraries—you might have missed a setup step where you need to provide a configuration object via an injection token (sometimes named something like OPTIONS).

• Rule out minification/mangling issues
  If you’re seeing this in a production build, the original token name might have been minified to just options. Try running your app in development mode (ng serve instead of a production build)—Angular will output unminified error messages that should show the full, original injection token name (e.g., MyCustomOptions or a library-specific token).

• Look for naming collisions
  Did you accidentally create a class or injection token named Options that’s conflicting with something else? For example, if you have:

  export class Options { /* ... */ }
  

  Make sure you’re providing this class in your module’s providers array if components/services are injecting it, or if it’s supposed to be an injection token, use InjectionToken instead of a plain class.

• Debug with a temporary provider
  If you’re still stuck, add a temporary provider to your AppModule to log where the Options injection is being requested:

  import { InjectionToken } from '@angular/core';
  
  // First, try to match the token—if it's a class, use the class; if it's a token, use the token
  export const OPTIONS_TOKEN = new InjectionToken<any>('options');
  
  @NgModule({
    providers: [
      {
        provide: OPTIONS_TOKEN, // Or use Options if it's a class
        useFactory: () => {
          // Log the stack trace to see who's requesting this
          console.trace('Options requested by:');
          return {}; // Provide a dummy value temporarily
        }
      }
    ]
  })
  export class AppModule { }
  

  When the app runs, check the browser console—you’ll get a full stack trace showing exactly which component/service is trying to inject Options.

Once you find the source, you can fix it by either:

• Adding the missing provider to your module or component’s providers array
• Importing the required module from a third-party library that provides the Options token
• Correcting the injection token name if you had a typo (e.g., @Inject(OPTIONS) instead of @Inject(Options))

内容的提问来源于stack exchange，提问作者techkuz