I’m currently working on a project where the front-end is built using Angular 16, while the back-end is in ASP.NET
The challenge I’m facing is debugging the Angular production code integrated within the ASP.NET environment.
Background: We load some settings on the default.exe page, and then we load the production build of our Angular application on the same page. Whenever we make changes to the Angular code, we have to rebuild the Angular app for production and then run the default.exe page to see the changes. While this process works fine for testing and deploying the application, debugging the production code has been quite challenging. With the minification and optimization done during the production build, it’s hard to trace issues and bugs. Although I have enabled source map.
Q: Is there a way to debug the Angular production code more effectively?
Q: Can we convert the production code into development code, perhaps by making some configuration changes?