Dependencies update coordination

[demurgos]

Following #31 and discussions with @bcoe, I plan to release a coverage based on different design decisions: using spawn-wrap, the inspector API and AST. To achieve this, I need to introduce updates to some dependencies. My high-level needs are stronger encapsulation and type annotations.

The goal is not to fork the dependencies but discuss my changes and try to merge them so they can benefit to everyone. I already know the end result I'd like to have, but did a large amount of refactoring to make the libraries more maintainable. Sending these end-results in block is overwhelming to [review] (and kinda rude) so I am planning to merge the changes gradually, sending small PRs, and discussing each of them. This is a long process across multiple repos. The goal of this issue is to keep track of these various PRs.

signal-exit

• fix(ci): use Travis for Windows builds tapjs/signal-exit#53
• feature(types): add type definitions tapjs/signal-exit#51

foreground-child

• chore: update dependencies tapjs/foreground-child#23
• feat: require Node 6 tapjs/foreground-child#24
• refactor: foregroundChild arguments normalization tapjs/foreground-child#25
• coverage: add tests for arguments normalization tapjs/foreground-child#30
• refactor: Accept parent process as argument to proxySignals tapjs/foreground-child#26
• refactor: IPC message forwarding tapjs/foreground-child#27
• refactor: avoid returns in module body tapjs/foreground-child#29
• refactor: use ES2015 tapjs/foreground-child#31

(more to come)

spawn-wrap

• feat: require Node 8 istanbuljs/spawn-wrap#78

(more to come)

[profnandaa]

cc. @bcoe

[profnandaa]

@demurgos - I have reviewed all and approved, waiting for Ben to check and merge.

[demurgos]

Hi,
I discussed with @bcoe: unfortunately he does not have much time for OSS currently but redirected me to @isaacs and @addaleax. Could one of you look at these PRs? @profnandaa already reviewed most of them and I took care to keep them simple.

I am almost done with my own coverage tool (see #31 ) but I really need some fixes. I am currently using my own forks but this is not an ideal solution.

I am available on the node-tooling Slack to discuss these PRs more easily.

[bcoe]

Please feel free to reopen if there's any continued work you'd like to do around this 👍

We've been inactive for quite some time, so going to close for now.