chore: add support to v16

[RafaelGSS]

Address: clinicjs/node-clinic#295

[mcollina]

lgtm

[mcollina]

lgtm

[RafaelGSS]

@mcollina The CI is failing for v16 because it has introduced a different behavior when using fs.createWriteStream. Look at the following reproducible code:

const fs = require('fs')
const stream = require('stream')

const processStatEncoder = new stream.Transform()
const out = processStatEncoder.pipe(fs.createWriteStream(`example-${process.version}`))
process.exit()

If you run it using v14 it will create the file, using v16 it doesn't create, looks like the fs.createWriteStream will create it in the next tick, however, since a process.exit() is found the file is never created. I mean, it only affects the tests, and I feel that it's correlated to: clinicjs/node-clinic#293 (comment).

I'll fix it by just running in the next tick, but it's important to note here.

[RafaelGSS]

The remaining tests I'm not able to reproduce locally. But looks like it's indeterministic since the creation. https://github.com/clinicjs/node-clinic-doctor/actions

[RafaelGSS]

@mcollina Can I merge it or should look at the flaky windows tests?

[RafaelGSS]

Well, looks that ba904ed fixes it.

Just for reference, it's needed because tap@15 uses node-preload under the hood on windows paths: https://github.com/cfware/node-preload/blob/master/hook-spawn.js#L16. Similar behavior of: clinicjs/node-clinic-bubbleprof#382 (comment).

I'm a bit worried about that change on tap@15, changing the node environment under the hood is quite worrying. (Jest feeling)