- ABP Framework version: v8.3
- UI Type: Angular
- Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..) / MongoDB
- Tiered (for MVC) or Auth Server Separated (for Angular): no
It used to be that we could only fire up ABP Suite and tell it to create an Angular application it that would be it. Now that option seems to be gone in ABP Suite and ABP Studio only seems to create an Angular application that won't even build due to several missing packages and also quite a lot of deprecated ones. Weirdly enough, creating single layer Angular application does not seem to have this problem, or at least that one you can build even though it also contains numerous packages marked as deprecated. This even if you deselect all additional modules like GDPR, chat etc.
Only using default settings in latest ABP Suite except that we selected Angular as UI and layered application and this is what we got
How are we supposed to create a new working layered Angular application in ABP Commercial 8.3?
Edit: Please note that we don't know exactly why some packages are marked as deprecated and if that is actually true, but still it won't even build when using the layered Angular template due to missing packages.
3 Answer(s)
-
0
Having looked further into this, it seems like packages.json is missing several dependencies including but not limited to @abp/ng.feature-management.
-
0
The packages really seem to be marked with deprecated, even though they were just recently updated
- @deprecated FeatureManagementModule is deprecated .
- @description use
provideFeatureManagementConfigfunction for config settings. - You can import directives and pipes directly whichs were belongs to FeatureManagementModule are switched to standalone.
https://www.npmjs.com/package/@abp/ng.feature-management/v/8.3.0
-
0
Even after you have done the necessary corrections to get the Angular app to even run, there seem to be numerous problems with lag, poor performance etc. This seem to happen in all Chromium based browser but not in Firefox. Notice how the left bar hides the content of the application, and also the very poor performance numbers. Also, when you click the "change container width" in a Chromium browser, nothing seems to happen, but when you do it in Firefox, you can see the changes directly. Also notice the large number of warnings reported.
Unless we are doing something really wrong here, it seems like the Angular template in ABP is a no go at the moment for various reasons. There could of course be other causes of this than ABP, but non of our other Angular applications display any problems like this running on the same dev machines, same browsers etc.
Edit:
Correction, it seems like the problems here are not caused by browser engine but rather browser width. It seems like for certain width, the LeptopX theme, at least for Angular, simply breaks which cause both visual distortion as well as at least some of the performance problems. This can be verified by simply adjusting the width of the browser windows (tested on Windows 11, Firefox, Chrome and Edge, all show the same behavior).
Edit 2:
It seems to be the LeptonX theme that is broken in general for certain screen width so those specific problems are probably not related to Angular, even though the other ones are. This is how it looks with Blazor
