No provider for InjectionToken CORE_OPTIONS! when upgrade ABP version 9.2.x #10293

4 Answer(s)

• 

  0

  AI-Bot created yesterday

  Support Team ABP Agent

  1. Solution

  The NullInjectorError: No provider for InjectionToken CORE_OPTIONS! and the “Cannot find the en locale file” error are both symptoms of the same root cause: Angular is not resolving the correct @abp/* / @volo/* packages (so the DI configuration from @abp/ng.core is never applied, and the locale files can’t be found).

  This exact issue is known on ABP 9.x Angular (see Microservice template case) and is fixed by normalizing the TypeScript paths so they point to node_modules.

  Do the following in your Angular app (the one that contains app.module.ts you shared):

  1. Edit tsconfig.json of the Angular app (usually apps/angular/tsconfig.json in microservice templates, or root tsconfig.json in single app):

     Add/merge these paths under compilerOptions:

  {
       "compilerOptions": {
         // ...existing options...
         "paths": {
           // keep your existing paths, then add/override these:
           "@abp/*": ["node_modules/@abp/*"],
           "@volo/*": ["node_modules/@volo/*"]
         }
       }
     }
  

  • If you already have @abp/* or @volo/* entries, make sure they only point to node_modules/@abp/* and node_modules/@volo/*, not to any local libs.

  2. Clean and reinstall dependencies

     From the Angular project folder:

  rm -rf node_modules
     rm -f package-lock.json yarn.lock
     # then
     yarn        # or npm install
  

  3. Rebuild and run

  yarn start  # or npm start
  

  4. Verify your root module setup

     Your AppModule’s core setup is already correct for ABP 9.2.x:

  CoreModule.forRoot({
       environment,
       registerLocaleFn: registerLocale(),
     }),
  

  Once @abp/ng.core is correctly resolved from node_modules, this will:

  • Provide CORE_OPTIONS (fixing the NullInjectorError).
  • Load the default en locale (fixing “Cannot find the en locale file”).

  After applying the paths fix and reinstalling dependencies, both errors should disappear on a fresh build.

  ---

  2. Sources

  • ABP Angular localization & culture files:
    https://abp.io/docs/latest/framework/ui/angular/localization

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  trang.huynh@lexarius.com created yesterday

  { "compileOnSave": false, "compilerOptions": { "baseUrl": "./", "outDir": "./dist/out-tsc", "sourceMap": true, "declaration": false, "downlevelIteration": true, "experimentalDecorators": true, "moduleResolution": "node", "importHelpers": true, "target": "ES2022", "module": "es2020", "lib": [ "es2018", "dom" ], "paths": { "@abp/*": ["node_modules/@abp/*"], "@volo/*": ["node_modules/@volo/*"], "@proxy": [ "src/app/proxy/index.ts" ], "@proxy/*": [ "src/app/proxy/*" ] }, "useDefineForClassFields": false, "skipLibCheck": true, "allowSyntheticDefaultImports": true }, "angularCompilerOptions": { "enableI18nLegacyMessageIdFormat": false }, }

  I tried, but same errors.

  Save Cancel
• 

  0

  AI-Bot created yesterday

  Support Team ABP Agent

  1. Solution

  The CORE_OPTIONS error is not caused by your tsconfig.json anymore (your paths look correct). In ABP Angular, this error is almost always due to version mismatches or an extra CoreModule.forRoot/import. Below is a concrete checklist that fixes the issue in 9.x projects.

  ---

  A. Normalize all ABP / Volosoft / Angular versions

  1. In your package.json, make sure all of these have the same minor version line:

  • @abp/ng.* → ~9.2.4
  • @volo/abp.ng.* → ~9.2.4
  • @volosoft/abp.ng.theme.lepton-x → ~4.2.4 (this is correct for ABP 9.2.x)
  • @volo/ngx-lepton-x.core → ~4.2.4
  • @angular/* → all the same major/minor (one line, e.g. all ~18.x.x or all ~19.x.x – but all must be identical)

  Make sure there is no different version of any of these packages pulled in indirectly; if you see any other version ranges (like ^9.1.x or ~9.0.x) for @abp, @volo or @volosoft in dependencies or devDependencies, change them to ~9.2.4 to match.

  In a very similar support case, the exact same CORE_OPTIONS error disappeared as soon as all @abp/*, @volo/* and the theme package were normalized to the same minor version.

  2. After editing package.json, fully clear and reinstall:

  # in the Angular project folder
  rm -rf node_modules .angular yarn.lock package-lock.json
  yarn cache clean || npm cache clean --force
  
  yarn        # or npm install
  yarn start  # or npm start
  

  ---

  B. Ensure CoreModule is imported only once with forRoot

  Check all your Angular modules for @abp/ng.core imports.

  1. In AppModule (root), it must be:

  CoreModule.forRoot({
    environment,
    registerLocaleFn: registerLocale(),
  }),
  

  2. In all other modules (shared/feature libraries), you must not call forRoot. If you import CoreModule there, it should be without forRoot:

  // ✅ allowed in feature/shared modules
  import { CoreModule } from '@abp/ng.core';
  
  @NgModule({
    imports: [
      CoreModule,      // WITHOUT .forRoot()
      // ...
    ],
  })
  export class SomeFeatureModule {}
  

  If you have any other CoreModule.forRoot(...) in the project (including inside your own libraries), Angular will create a separate injector that does not get the CORE_OPTIONS from your main AppModule, and RestService (from @abp/ng.core) will fail with exactly the error you see.

  So:

  • Search the whole solution for CoreModule.forRoot and keep it only in AppModule.
  • Replace any other occurrences with just CoreModule.

  ---

  C. Double‑check you are not using local/custom ABP Angular package sources

  The support context for this error also shows it happens when a project:

  • Has local copies of ABP / Volosoft Angular packages, or
  • Has tsconfig paths pointing to those local copies.

  You already set:

  "paths": {
    "@abp/*": ["node_modules/@abp/*"],
    "@volo/*": ["node_modules/@volo/*"],
    "@proxy": [ "src/app/proxy/index.ts" ],
    "@proxy/*": [ "src/app/proxy/*" ]
  }
  

  Now verify that:

  • There are no other tsconfig*.json files (in libs/projects) that override @abp/* or @volo/* to some local folder.
  • You are not checking in customized ABP/Volosoft Angular package source under your repo and referencing it via paths.

  If you find any path like "@volo/abp.ng.identity": ["projects/identity/src/public-api.ts"] etc., remove those mappings (or rename your custom libs to a different prefix) so @abp/* and @volo/* always resolve to node_modules.

  ---

  D. Fix the “Cannot find the en locale file” error

  This is usually resolved automatically once CoreModule.forRoot + registerLocaleFn run from the correct @volo/abp.ng.language-management version, but verify:

  1. Import and use registerLocale exactly like this (which you already do):

  import { registerLocale } from '@volo/abp.ng.language-management/locale';
  
  CoreModule.forRoot({
    environment,
    registerLocaleFn: registerLocale(),
  }),
  

  2. Ensure the localization assets are copied:

  Your angular.json (or workspace config) app’s assets section should include ABP localization assets (in a 9.x Angular app this is done by the template). Make sure these lines (or their equivalent) exist for your main app:

  "assets": [
    "src/favicon.ico",
    "src/assets",
    {
      "glob": "**/*",
      "input": "node_modules/@abp/ng.theme.shared/assets",
      "output": "/assets"
    }
  ]
  

  There needs to be an en locale JSON under /assets (e.g. /assets/abp-localization/en.json or similar). If the assets from @abp/ng.theme.shared are not copied, you get the “Cannot find the en locale file” error.

  Rebuild after any change to angular.json:

  yarn start --configuration development  # or just yarn start (depending on your setup)
  

  Once the versions are normalized, CoreModule.forRoot is only in AppModule, and localization assets are in place, both:

  • NullInjectorError: No provider for InjectionToken CORE_OPTIONS!
  • Cannot find the en locale file.

  should be resolved on a clean build.

  ---

  2. Sources

  • ABP Angular Localization (adding cultures & locale files)
    https://abp.io/docs/latest/framework/ui/angular/localization

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  trang.huynh@lexarius.com created yesterday

  Support team, please.

  Save Cancel