Skip to content
This repository was archived by the owner on Dec 8, 2018. It is now read-only.

Dedicated page for JavaScript invoked on server-side #404

Closed
rosieks opened this issue Aug 18, 2017 · 4 comments
Closed

Dedicated page for JavaScript invoked on server-side #404

rosieks opened this issue Aug 18, 2017 · 4 comments

Comments

@rosieks
Copy link

rosieks commented Aug 18, 2017

SpaServices project provides ability to run JavaScript on server. When such invocation failed the following error is displayed.

image

It would be nice to have dedicated page that focus on JavaScript error and provide nicefied stacktrace, current npm version, etc

@Eilon
Copy link
Contributor

Eilon commented Aug 23, 2017

@SteveSandersonMS any thoughts on this? We've been thinking of some diagnostics pages extensibility in general, for example: #403

@SteveSandersonMS
Copy link
Member

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 NodeInvocationException and pull it out.

@Eilon Eilon added this to the 2.1.0 milestone Aug 24, 2017
@Eilon
Copy link
Contributor

Eilon commented Aug 24, 2017

Ok, we'll consider something for 2.1.0 then.

@aspnet-hello
Copy link

This issue was moved to dotnet/aspnetcore#2585

@aspnet aspnet locked and limited conversation to collaborators Jan 2, 2018
@aspnet-hello aspnet-hello removed this from the 2.1.0-preview1 milestone Jan 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants