Skip to content

Strict typing for sendMessage and onMessage everywhere #73

@mstephen19

Description

@mstephen19

We've got commented out a type named Acceptable, which encompasses all values that can be send via parentPort.postMessage and worker.postMessage without hitting a runtime error. Instead of any, this type should be used instead for the sendMessage and onMessage methods on various implementations.

Metadata

Metadata

Assignees

Labels

improvementAn existing feature can be improved

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions