Skip to content

ErrorEvent.error is null when handling an uncaught error from a worker #27753

Open
@cowboyd

Description

Version: Deno 2.1.6

When handling an uncaught error from the main thread, the error field on the resulting error event is null. The expected behavior is that it would be, if not the exact error, an error with the same message and perhaps a cause indicating that it was thrown in the worker.

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