Diagnostics for server side rendering (Angular in particular)q #396

New Issue

fergalmoran · 2025-08-09T17:16:07Z

fergalmoran commented

2025-08-09 17:16:07 +00:00

Originally created by @pauloya on 9/29/2017

What is the best practice for diagnosing problems with an angular app while being rendered on the server in production?
Is there a way to see what is written in the console, and is there a way to get the callstack of an exception just like I get on the browser?
I noticed that there is NodeInstanceOutputLogger, can this help getting more diagnostics? and is there an example of an implementation for an ILogger I could use?

Thanks

*Originally created by @pauloya on 9/29/2017* What is the best practice for diagnosing problems with an angular app while being rendered on the server in production? Is there a way to see what is written in the console, and is there a way to get the callstack of an exception just like I get on the browser? I noticed that there is `NodeInstanceOutputLogger`, can this help getting more diagnostics? and is there an example of an implementation for an ILogger I could use? Thanks

fergalmoran closed this issue

2025-08-09 17:16:07 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#396