Add `hasRef` to `worker_threads.Worker`

[SimenB]

What is the problem this feature will solve?

Jest has a --detect-open-handles flag which attempts to figure out (using async_hooks) what resources (timer/server etc.) are preventing a test run/node from exiting. To avoid false positives we perform filtering before presenting the list to the user. One of those things is to check if a Timer has been unrefed or not, via Timer.hasRef.

However, Workers have no hasRef, even though they have the {un}ref pair, so Jest will currently print false positives for Workers that have had unref called.

What is the feature you are proposing to solve the problem?

Add Worker.hasRef similar to the Timer API.

What alternatives have you considered?

No response

[targos]

What about other APIs that have an unref function? ChildProcess, FSWatcher, etc.

[SimenB]

I haven't gotten a bug report in Jest about them, so I have no opinion 😀

On a more serious note, I think it makes sense for ref, unref and hasRef to always exist together.

[benjamingr]

@SimenB would you be interested in contributing a PR? I am happy to guide you, the code is in io.js and worker.js mostly :)

[SimenB]

Io.js, that's a blast from the past! Happy to contribute it if it'll get accepted 🙂