Skip to content

fail not catched when error is unserializable #49

@kapouer

Description

@kapouer

Hi,
i happen to call browserify in a worker node: upon failure it returns an error with a lot of additional structures.
It took me a while to realize I had to rewrite the error using:

const err2 = new Error(err.message);
err2.code = err.code;
err2.stack = err.stack;
reject(err2);

i wonder if there is a way for worker-nodes to avoid the headache.

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