I have removed the .suite folder and tried creating a new entity with just one property. I have the same error about 'npm install'. Clicking save & generate a second time does not show the error anymore but still no frontend code gets generated. ABP CLI & Suite are both 7.3.1 however the solution itself is still at 7.3.0.
I have also created a new test solution from scratch and that one has version 7.3.1. The new one failed to build due to it requiring Volo.Abp.AspNetCore.MultiTenancy version 7.3.2 instead of 7.3.1. Manually changing the version and adding an entity generated frontend code as well.
So I think the issue or one of the issues is with the solution version being 7.3.0.
What is the best way to update the solution to 7.3.1?
Thank you for your reply.
I have tried your suggestion, however it has the same behavior like before.
Running yarn install in C:\Repos\ClimateCamp\angular\.suite does something but then I have the exact first error about 'npm install'. Shouldn't the command be executed in C:\Repos\ClimateCamp\angular\.suite\schematics?
But even after running it in the \schematics directory, there is the same behavior as after running npm install --legacy-peer-deps.
I have updated ABP CLI and ABP Suite to 7.3.1, however the solution is still 7.3.0. In the ABP Suite UI, selecting 'Switch to stable packages' does bump the solution to 7.3.1, however the project fails to even build.
If I'm missing something, please let me know.
Thank you.