developit/workerize-loader

Transferable support

Open

#51 opened on Aug 25, 2018

View on GitHub
 (6 comments) (6 reactions) (0 assignees)JavaScript (2,296 stars) (111 forks)batch import
enhancementgood first issuehelp wanted

Description

Hi! Do you think you could include a way to pass Transferable objects correctly? It would be great to be able to return a MessagePort so that the function can return a stream instead of a single value.

Contributor guide

Tech stack
javascript
Domain
build systemtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Web Workers basicspostMessage APIworkerize loader codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests support for Transferable objects, specifically MessagePort, in workerize loader. Currently, the loader handles serialization via structured clone, but Transferables are not passed. Research should examine the loader's generated worker code (likely in src/index.js) to see how postMessage is called. Consider adding an option to specify transferable objects in the module exports, similar to how other libraries handle this. Review the comments on the issue for any suggested approaches. No linked PR exists.