Recommend using promisify-child-process instead?

[jedwards1211]

Awhile ago I hurriedly rewrote this library to add some features and released it as promisify-child-process. Aside from impatience with making PRs and waiting for them to get merged, I wanted to:

• Also promisify execFile and fork
• Export the sync methods so that it can be a drop-in replacement for child_process
• Include flow type defs
• Have a full CI setup with semantic-release

I realize now that I created unfortunate fragmentation in the ecosystem and I should try to merge my code into this project (assuming you wouldn't prefer to deprecate this package in favor of mine).

What do you guys want me to do? The easiest thing would be making a PR that essentially replaces all code in this repo with mine (it would not cause any breaking changes to the API) but that might seem a bit heavy-handed.

[harrysarson]

Just to warn you @jedwards1211, I am not sure this repo is actively maintained at the moment.
I might be wrong but I haven't seen any activity here in a while. 😞

[jedwards1211]

Oh okay. Maybe I should just start promoting mine as a replacement then?
https://github.com/jcoreio/promisify-child-process