Activities of "rshapiro"

AI answer did not help but pointed me at table which helped me to answer myself

The browser builder is still supported, so you can keep it as is. After the upgrade, you should not face the build errors you mentioned. Let us know if you need further assistance!

Thanks. The update to Angular 19 did the trick. However, you should add the fact that the update to Angular 19 is required with the update to v9 into the migration guide and outline the actions to take on the couple of optional updates that are part of the Angular 19 updates.

Hello,

Since then ABP 9.1 uses Angular v19, you will need to update your application accordingly. You can follow this guide
https://angular.dev/update-guide

Thank you for your cooperation.

Hi,

Are you certain that updating to Angular 19 will correct this? One of the other forum posts I linked in my initial question indicates they had this issue even with Angular 19.

Going through the Angular 19 upgrade and it's indicating that there's an optional migration to migrate the project to the new build system. Is this something we should or should not do?

Hello,

Since then ABP 9.1 uses Angular v19, you will need to update your application accordingly. You can follow this guide https://angular.dev/update-guide

Thank you for your cooperation.

Hi,

Are you certain that updating to Angular 19 will correct this? One of the other forum posts I linked in my initial question indicates they had this issue even with Angular 19.

Hi,

Out angular team will help you on this topic.

Until then, can I ask have you cleaned node_modules and remove yarn.lock/packages.lock file and install all the packages cleanly?

Yes, I had cleared the node_modules but not the yarn.lock file.