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

Call to Node module failed with error: Error: [object Object] = Bad Error Message #1193

Description

@JohnGalt1717

As is clearly the case when this error message is thrown by the Prerenderer.ReturnToString there is an object with the full error message available from node but it isn't properly parsed from json and thus we don't actually know what failed.

It would be really nice if this was parsed properly by the spa services and we got a real error message.

Thanks!

Activity

  1. SteveSandersonMS commented on Aug 21, 2017

    @SteveSandersonMS
    Member

    I agree that's not a good error message!

    The better news is we improved the error reporting a while ago. As far as I can tell, this should already be fixed in the current version. Grepping through the sources, I don't see any strings prefixed with Error: any more.

    However, if you have any way to repro this bad error message with a current .NET Core 2.0 SDK app, please let us know!

  2. JohnGalt1717 commented on Aug 26, 2017

    @JohnGalt1717
    Author

    Hi @SteveSandersonMS it is indeed better under .net core 2 after our upgrade. It's still like trying to find needles in a haystack. I wish there was a recipe on the Vs code site for hooking up .net core, chrome and nodejs debuggers in vs code to debug what's going on in node. (the other two are easy) Getting node debugging working has still been elusive here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions