Skip to content

Errors with Typescript call stacks #14

@thekevinbrown

Description

@thekevinbrown

When there's an error from the main process, errors are reported referencing line numbers of JS files in the dist folder, e.g. the compiled output:

(node:59233) UnhandledPromiseRejectionWarning: TypeError: settings_1.Settings.get(...) is not a function or its return value is not iterable
    at SomeCode (/<project path>/dist/main/main.js:231:44)
...etc
    at process._tickCallback (internal/process/next_tick.js:68:7)

It'd be awesome if these could be reported back to the developer with source maps so there's a Typescript file and line number there.

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