Hello,
You may obtain the source code via ABP Suite, as outlined in the official documentation:
https://abp.io/docs/latest/suite/source-code
If your work involves configuration or settings, the Setting Management module may also be of interest.
Alternatively, to access the source code and replace the current identity package integration for customization purposes, you may execute the following command:
abp add-package @volo/abp.ng.identity --with-source-code
You need to run this command within your Angular project directory. This will include the package along with its source code in your project. Once added, you can refer to the IdentitySettingsComponent for any necessary modifications.
If you need any further assistance, please do not hesitate to reach out.
Hello,
Adding the missing import should resolve the issue. Could you please try deleting all temporary files and folders—such as .nx, .angular, node_modules, tmp, dist, yarn.lock, etc.—and then reinstall dependencies by running yarn again?
Other than that, I did not notice any issues in the project you shared—it appears to be working as expected.
In the meantime, could you also share the versions of Node and Yarn you are using?
Hello again, I sent you an e-mail.
Hello, and thank you for providing additional details about your issue. I recommend accessing the source code by running the following command:
abp add-package @volo/abp.commercial.ng.ui --with-source-code
This will allow you to review the BackToImpersonatorNavItemComponent and ImpersonationService, which contain the relevant functionality logic.
You can let us know if you need any further assistance.
Could you provide an e-mail address, so that I can share the folder? Here is my address: sumeyye.kurtulus@volosoft.com
I see that this import is missing for InternetConnectionStatusComponent, you will need to add this import to your app.module.ts
import {
InternetConnectionStatusComponent,
} from '@abp/ng.theme.shared';
I have granted you the permission. I will also be checking your sample and get back to you as soon as possible. Thank you for your cooperation.
Hello! Thank you for sharing more details about your issue.
It looks like execa might not be installed correctly.
You can check if it is available by running:
node --eval "console.log(await import.meta.resolve('execa'))" --input-type=module
Alternatively, you can look for execa in the angular/.suite/schematics/package-lock.json file.
If it is not installed, try running npm install inside the angular/.suite/schematics directory.
If the issue persists, I can send you a working .suite file. Feel free to let me know if you would like that or need further help!
Hello again,
I have been unable to reproduce the issue on my end. To help investigate further, I have created a simple application using the command:
abp new Acme.BookStore -u angular
Here is the project link: https://drive.google.com/file/d/1b6ykAO-yoFci-v8zQgBpZ0X4uEEkVKk0
To better understand the cause of the issue, it would be helpful if you could share a sample project where the problem occurs. Additionally, please let me know if there were any custom changes you made that might contribute to the issue. It is also possible that the problem is related to a version mismatch between Node.js and Angular.
If you could provide these details, we’ll be better equipped to assist you further.
Thank you for your cooperation.
Thank you for providing extra details on that. However, I could not produce the same problem on my end. Could you please share a minimal, reproducible example so we can assist you further? You can send it through this e-mail address sumeyye.kurtulus@volosoft.com
