-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Dedicated page for JavaScript invoked on server-side #2585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From @Eilon on Wednesday, August 23, 2017 12:11:12 AM @SteveSandersonMS any thoughts on this? We've been thinking of some diagnostics pages extensibility in general, for example: aspnet/Diagnostics#403 |
From @SteveSandersonMS on Wednesday, August 23, 2017 12:02:31 PM It would definitely be good to present this information more readably - the stack trace at least. If the new diagnostics extensibility point issued a call back to get the nicely formatted error info, passing the original exception, then it would be easy enough to embed whatever info we need into the |
From @Eilon on Thursday, August 24, 2017 10:33:38 AM Ok, we'll consider something for 2.1.0 then. |
Formatting urls when using the WebSocketsTransport (#2571)
Hi. Thanks for contacting us. |
It seems this has not been fixed and will not be fixed? Or am I missing something? This would be very helpful. Atm this makes it very cumbersome to develop anything using NodeServices, since it's always guesswork to figure out where errors come from. |
From @rosieks on Friday, August 18, 2017 1:24:13 PM
SpaServices project provides ability to run JavaScript on server. When such invocation failed the following error is displayed.
It would be nice to have dedicated page that focus on JavaScript error and provide nicefied stacktrace, current npm version, etc
Copied from original issue: aspnet/Diagnostics#404
The text was updated successfully, but these errors were encountered: