Hi there!
I’m currently working on built-in Worker support (as in, threaded workers rather than cluster/child process) in Node.js, and there is only little left to do for that. (It’s basically just porting over changes from a fork of Node, Ayo.)
Now, the most natural way to expose that functionality seems through a built-in worker module. Since you own that name on npm, and your module would thus conflict with this: Would you be willing to rename/move this to another module name (similar to what we did for http2)? I realize it’s a pretty great name to get, but on the other hand I’d like to a natural name for the built-in module.
Let me know if you have any thoughts/questions about this!
Hi there!
I’m currently working on built-in Worker support (as in, threaded workers rather than cluster/child process) in Node.js, and there is only little left to do for that. (It’s basically just porting over changes from a fork of Node, Ayo.)
Now, the most natural way to expose that functionality seems through a built-in
workermodule. Since you own that name onnpm, and your module would thus conflict with this: Would you be willing to rename/move this to another module name (similar to what we did forhttp2)? I realize it’s a pretty great name to get, but on the other hand I’d like to a natural name for the built-in module.Let me know if you have any thoughts/questions about this!