ABP Framework version: v8.1.1 UI Type: Angular Database System: EF Core SQL Server Tiered (for MVC) or Auth Server Separated (for Angular): no Steps to reproduce the issue: Tried to utilize abp modules in my angular ui project (that I have to integrated with) for the latest dependency tree (if you want to update your package.json tree use **npm ncu -u **command from https://www.npmjs.com/package/npm-check-updates): this is the updated tree: "dependencies": { "@abp/ng.components": "~8.1.1", "@abp/ng.core": "~8.1.1", "@abp/ng.oauth": "~8.1.1", "@abp/ng.theme.shared": "~8.1.1", "@angular/animations": "~17.3.8", "@angular/cdk": "~17.3.8", "@angular/common": "~17.3.8", "@angular/compiler": "~17.3.8", "@angular/core": "~17.3.8", "@angular/forms": "~17.3.8", "@angular/language-service": "~17.3.8",
First the project showed an infinite loop in ts-toolbelt that the **ng.core *depends on : Type instantiation is excessively deep and possibly infinite
so I have added a resolution package for it to udpate ts-toolbelt like that: ,
"resolutions": {
"ts-toolbelt": "9.6.0"
},
Now It shows this warning on the output using the latest libraries when running yarn start:
1:22:34 PM [vite] warning:
C:/Users/MSI-1/source/repos/UWAbp/src/UWAbp.Web.Angular/.angular/cache/17.3.7/vite/deps/@volo_abp__ng__language-management_locale.js
42 | / webpackInclude: //\.(mjs|js)/ /
43 | / webpackExclude: /[/\]global|extra/ /
44 | @angular/common${localePath}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
45 | ).then((val) => {
46 | let module = val;
The above dynamic import cannot be analyzed by Vite.
See https://github.com/rollup/plugins/tree/master/packages/dynamic-import-vars#limitations for supported dynamic import formats. If this is intended to be left as-is, you can use the / @vite-ignore */ comment inside the import() call to suppress this warning.
Plugin: vite:import-analysis File: C:/Users/MSI-1/source/repos/UWAbp/src/UWAbp.Web.Angular/.angular/cache/17.3.7/vite/deps/@volo_abp__ng__language-management_locale.js?v=a7983de3
on the Browser Console it shows these two warnings: You should add @abp/ng-oauth packages or create your own auth packages.
warningMessage @ abp-ng.core.mjs:156 Show 1 more frame Show less abp-ng.core-locale.mjs:44 Cannot find the en locale file. You can check how can add new culture at
Can you please update your npm packages to fix the npm modules problem,I tried to update, downgrade etc.. delete cache but no solution it seems that the npm packages are corrupted even though projects generated using abp suite are working fine but when trying to use @abp/ng.core for example it doesn't load as it doesn't see the en locale as the package has a bug also fix the ts-toolbelt issue with the latest angular compiler The Problem is mainly due to problems with language management and core modules which renders the core module not instantiated and I cannot use the proxy or any thing
3 Answer(s)
-
1
Hello,
try to downgrade Angular version to 17.1 Delete
yarn.lockfile and rerunyarncommand then try to run application. check similar issue https://support.abp.io/QA/Questions/7086/Angular-app-does-not-working-after-upgrade-to-811thanks
-
0
@Anjali_Musmade the locale issue remains the same no matter if I have upgraded or downgraded ? 17.1 /* webpackExclude: /[/\]global|extra/ / 44 |
@angular/common${localePath}| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 45 | ).then((val) => { 46 | let module = val; The above dynamic import cannot be analyzed by Vite. See https://github.com/rollup/plugins/tree/master/packages/dynamic-import-vars#limitations for supported dynamic import formats. If this is intended to be left as-is, you can use the / @vite-ignore */ comment inside the import() call to suppress this warning.Plugin: vite:import-analysis File: C:/Users/MSI-1/source/repos/UWAbp/src/UWAbp.Web.Angular/.angular/cache/17.1.4/vite/deps/@volo_abp__ng__language-management_locale.js?v=f5fb5be9 chunk-PEQT6LCE.js?v=1b67697c:62 You should add @abp/ng-oauth packages or create your own auth packages. chunk-PEQT6LCE.js?v=1b67697c:75 Cannot find the en locale file. You can check how can add new culture at
-
0
Hello again,
could you please try this once https://support.abp.io/QA/Questions/5026/Starting-Angular---cleanfresh-project#answer-3a0b0dc4-5baa-df28-682b-e9356fdfc079 if it doesn't help you could you please share a sample project on support@abp.io
thanks
