Hello again,
Thank you for sharing the details. The issue is caused by these two TypeScript options: strict and isolatedModules.
If you do not need them for a specific reason, I recommend disabling them to resolve the error.
I don’t think this is related to the TypeScript configuration, but rather to the changes made in the proxy class generation logic in ABP 10.x, as described here: https://abp.io/support/questions/10400/ABP-10-Angular-proxy-required-C-fields-generated-as-optional-in-TypeScript
I asked because configuration mismatches can sometimes lead to issues like this.
As mentioned, this update was made deliberately, as explained in the issue. Could you also clarify whether you are using the npm-installed version of the packages or if you embedded the project’s source code directly?
Hello,
Thank you for the detailed explanation of the issue. It appears that the problem has been resolved on the backend side.
From what I understand, the backend defines tags as a single string in the Suite description, but then overrides it in C# as a list of strings. Because of this inconsistency, the proxy generator correctly reports the mismatch, and TypeScript raises an error.
To resolve the issue, the backend contract needs to be consistent. You can either keep tags as a string everywhere, or model it as a list/array of strings throughout the system. If a serialized string is required for storage purposes, it should be exposed as a separate property with a different name that is not part of the public DTO.
Once the backend contract is clean and consistent, the generated Angular proxies should also work correctly.
You can let us know if you need further assistance. Thank you for your cooperation.
Hello,
Thank you for providing additional details about the issue. It may be related to a mismatched TypeScript version or the configuration in your tsconfig. Could you please share your TypeScript version and the relevant tsconfig settings if possible?
Thank you for your cooperation.
Hello,
Thank you for yor kind interest and contribution. As you have also explained the server treats tenant timezone as DST‑aware. However, The Angular pipe is the only place that forces “standard offset only” for display when an IANA zone like US/Pacific is set intentionally.
So, changing the pipe to use DST‑aware formatting by default (e.g. by calling format() instead of formatDateWithStandardOffset()) would align with the server and with user expectations for IANA zones and would fix the “one hour behind after DST” issue.
You can also consider contributing a backward-compatible change (e.g. an optional parameter on abpUtcToLocal to use DST-aware formatting, or a dedicated DST-aware pipe). You can find details in this contribution guide.
You can let us know if you need further assistance. Thank you for your cooperation.
If you encounter an error similar to the following:
// root_effect_scheduler.mjs:3637
❌ ERROR ɵNotFound: NG0201: No provider found for `InjectionToken CORE_OPTIONS`. Find more at https://v20.angular.dev/errors/NG0201
as also mentioned here, you can resolve the issue by adding the following resolutions to your package.json:
"resolutions": {
"@ng-bootstrap/ng-bootstrap": "~19.0.0",
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3"
}
https://gist.github.com/sumeyyeKurtulus/6111671cf4f1773c1b8c1f354631087a
I am getting such error after updating my version to 10.0.x.
// root_effect_scheduler.mjs:3637
❌ ERROR ɵNotFound: NG0201: No provider found for `InjectionToken CORE_OPTIONS`. Find more at https://v20.angular.dev/errors/NG0201
Hello again,
I apologize for overlooking the project in your original question. After reviewing the project you shared, I noticed that some paths in the tsconfig.json file redirect to node_modules. This approach is no longer supported. You can find more details here:
https://abp.io/community/articles/angular-library-linking-made-easy-paths-workspaces-and-5z2ate6e#how-path-references-worked-before-the-new-angular-application-builder
/* To learn more about this file see: https://angular.io/config/tsconfig. */
{
"compileOnSave": false,
"compilerOptions": {
// ...
"paths": {
"product-service": ["src/product-service/public-api.ts"]
// "@abp/*": ["node_modules/@abp/*"],
// "@volo/*": ["node_modules/@volo/*"]
},
"useDefineForClassFields": false
},
}
I also noticed that some package versions are not aligned. In particular, the Angular-related packages and the TypeScript version should match specific compatible versions. Unless you have a specific reason to use different versions, I recommend aligning them as follows:
{
"name": "angular-starter",
"private": true,
"engines": {
"node": "^22.0.0"
},
//...
"resolutions": {
"@ng-bootstrap/ng-bootstrap": "~19.0.0",
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3"
},
"dependencies": {
"@abp/ng.components": "~10.0.3",
"@abp/ng.feature-management": "~10.0.3",
"@abp/ng.core": "~10.0.3",
"@abp/ng.oauth": "~10.0.3",
"@abp/ng.setting-management": "~10.0.3",
"@abp/ng.tenant-management": "~10.0.3",
"@abp/ng.theme.shared": "~10.0.3",
"@abp/ng.theme.lepton-x": "~5.0.3",
"@angular/animations": "~20.0.0",
"@angular/common": "~20.0.0",
"@angular/compiler": "~20.0.0",
"@angular/core": "~20.0.0",
"@angular/forms": "~20.0.0",
"@angular/localize": "~20.0.0",
"@angular/platform-browser": "~20.0.0",
"@angular/platform-browser-dynamic": "~20.0.0",
"@angular/router": "~20.0.0",
//...
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3",
"@volo/abp.ng.audit-logging": "~10.0.3",
"@volo/abp.ng.chat": "~10.0.3",
"@volo/abp.ng.file-management": "~10.0.3",
"@volo/abp.ng.gdpr": "~10.0.3",
"@volo/abp.ng.identity": "~10.0.3",
"@volo/abp.ng.language-management": "~10.0.3",
"@volo/abp.ng.openiddictpro": "~10.0.3",
"@volo/abp.ng.saas": "~10.0.3",
"@volo/abp.ng.text-template-management": "~10.0.3",
"@volosoft/abp.ng.theme.lepton-x": "~5.0.3",
//...
},
"devDependencies": {
"@abp/ng.schematics": "~10.0.3",
"@angular/build": "~20.0.0",
"@angular-eslint/builder": "~20.0.0",
"@angular-eslint/eslint-plugin": "~20.0.0",
"@angular-eslint/eslint-plugin-template": "~20.0.0",
"@angular-eslint/schematics": "~20.0.0",
"@angular-eslint/template-parser": "~20.0.0",
"@angular/cli": "~20.0.0",
"@angular/compiler-cli": "~20.0.0",
"@angular/language-service": "~20.0.0",
"@types/file-saver": "^2.0.7",
"@types/jasmine": "~3.6.0",
"@types/jszip": "^3.4.0",
"@types/node": "^20.17.16",
"@typescript-eslint/eslint-plugin": "^8.50.0",
"@typescript-eslint/parser": "^8.50.0",
//...
"typescript": "~5.8.0"
}
}
Hello,
Thank you for explaining the issue in detail. It may be related to a misconfigured installation. Could you add the following resolutions to your package.json and try reinstalling?
"resolutions": {
"@ng-bootstrap/ng-bootstrap": "~19.0.0",
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3"
},
You can let us know if you need further assistance. Thank you for your cooperation.
Hello,
Thank you for reaching out again. If you could provide an e-mail address and a target version, I can send the source code for this package.
Thank you for your cooperation.
