Hello, As you may notice from the template, the new Expo version has been applied, and the overall structure has been updated accordingly. We have also addressed the issues you mentioned. I recommend reviewing the latest documentation, which explains the updated structure in detail: 👉 https://abp.io/docs/10.0/framework/ui/react-native?Architecture=Tiered
If you encounter any other issues, I will be happy to assist further. Thank you for your cooperation.
We have included the latest implementations within the latest releases of ABP Studio. You can check the release notes here.
Thank you again for taking your time to send me a project. I have checked it and followed these steps:
Rollbacked to application builder system by running this command under apps > angular directory
Then added this missing configuration in angular.json
{
"projects": {
"architect": {
"build": {
"options": {
"browser": "projects/abp-solution3/src/main.ts",
},
},
}
},
},
}
I run this command under angular directory to add a library
npx ng g @abp/ng.schematics:create-lib --package-name management-service --is-secondary-entrypoint false --template-type standalone --override true
Here are my related package versions
➜ ~ npm -v :: 10.9.2 ➜ ~ node -v :: v22.16.0 ➜ ~ yarn -v :: 1.22.22
I am also sending the project back that may help you go through:
https://drive.google.com/file/d/10kVEyn2JBxq1ojRnDvjfeJqpfjtp8UPW/view?usp=sharing
Thank you for checking both ways and responding.
I have used this command to test this issue, abp new AbpSolution1 -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management . However, both ways worked on my side. Did the library creation command failed again? Or, is that another issue occured while generating the entity?
If you prefer sending a minimal, reproducible example, I can also test it on my side. Here is my e-mail address: sumeyye.kurtulus@volosoft.com.
I can suggest you to delete temporary files under main angular directory that are node_modules, yarn.lock, .angular etc. and then reinstall the packages.
If this does not work, you can try keeping the application builder configurations and add the following property in angular.json:
{
"projects": {
"architect": {
"build": {
"options": {
"browser": "projects/ticket9953/src/main.ts",
},
},
}
},
},
}
Could I also get some information about the resolution date for this error? Since many of our projects are progressing on this structure, we don't want to experience problems in our projects.
I understand your urgency. However, I cannot provide an exact time for the next release as we plan them frequently. You can follow this link https://abp.io/docs/latest/studio/release-notes
I hope this workaround works. You can let us know if your need further guidance.
Hello,
Thank you for reporting this problem. We will be fixing the related issue on the next patch release that you can follow the process through these links https://github.com/abpframework/abp/releases, https://abp.io/docs/latest/studio/release-notes
I can temporarily suggest a rollback to the browser build system. For this, you need to update the related parts in your angular.json as follows: (you can also check this documentation that would be helpful https://angular.dev/tools/cli/build-system-migration)
{
...
"projects": {
"ticket9953": {
"projectType": "application",
"schematics": {
...
},
"root": "projects/ticket9953",
"sourceRoot": "projects/ticket9953/src",
"prefix": "app",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:browser",
"options": {
"outputPath": "dist/ticket9953",
"index": "projects/ticket9953/src/index.html",
"main": "projects/ticket9953/src/main.ts",
"polyfills": "projects/ticket9953/src/polyfills.ts",
...
},
"configurations": {
...
"development": {
"buildOptimizer": false,
"optimization": false,
"vendorChunk": true,
"extractLicenses": false,
"sourceMap": true,
"namedChunks": true
}
},
...
},
"serve": {
"builder": "@angular-devkit/build-angular:dev-server",
...
},
"extract-i18n": {
"builder": "@angular-devkit/build-angular:extract-i18n",
...
},
"test": {
"builder": "@angular-devkit/build-angular:karma",
...
},
}
},
},
}
You need to replace @angular/build with @angular-devkit/build-angular dependency in your package.json file.
After reinstalling the packages in the root angular directory, you can create a library for your service using this command npx ng g @abp/ng.schematics:create-lib --package-name management-service --is-secondary-entrypoint false --template-type standalone --override true
Then, you can use suite for creating more features.
I am also processing a refund for your ticket. You can let us know if you need further assistance. Thank you for your cooperation.
Hello,
This answer may solve your problem: https://abp.io/qa/questions/9674/3a1b61b3-1e0a-ab46-a3ae-8dd97adc6a0d
If your application is using the standalone structure, you need to use the providers array in app.config.ts file instead.
You can let us know if you need further assistance. Thank you for your cooperation.
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(),
})
),
//...
],
};
Hello,
I am using a project generated by using the latest ABP template. However, the browser throws such error
Hello,
We have identified the same problem on our side. I can recommend you to migrate to the new application builder using this command:
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": {
},
"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(),
})
),
//...
],
};
I will also be processing a refund for your ticket. Thank you for your cooperation.
