0
sumeyye.kurtulus created
Support Team
Angular Expert
1 Answer(s)
-
0
Hello,
We have identified the same problem on our side. I can recommend you to migrate to the new application builder using this command until we publish an official fix:
yarn ng update @angular/cli --name use-application-builder
Here is the official reference: https://angular.dev/tools/cli/build-system-migration#automated-migration-recommended
After that, you need to remove the paths inside the
tsconfig.json
file{ "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": { // do not register abp paths here }, "useDefineForClassFields": false }, "angularCompilerOptions": { "enableI18nLegacyMessageIdFormat": false } }
You can also use the es build for the localization registration inside
app.config.ts
import { registerLocaleForEsBuild } from '@abp/ng.core/locale'; export const appConfig: ApplicationConfig = { providers: [ //... provideAbpCore( withOptions({ environment, registerLocaleFn: registerLocaleForEsBuild(), }) ), //... ], };