fix: upgrade foreground-child dependency

[bcoe]

@addaleax @jamestalmage mind giving this a spin while builds run?

[jamestalmage]

spawn-wrap still depends on [email protected]

[addaleax]

Looks good locally and I think bundling an npm3-style tree should take care of the old version that spawn-wrap depends on, right?

[bcoe]

@jamestalmage @addaleax my plan is to bundle on a [email protected] tree, which solves some singleton issues with our dependencies -- but! I think we should be fine as long as I re-install everything prior to publish? spawn-wrap isn't itself bundled or pinned.

[addaleax]

I guess that should work. If the copy of foreground-child in spawn-wrap’s dependencies is still outdated after that for some reason, you can probably also just remove it and let spawn-wrap use the top-level one.

[jamestalmage]

Yeah - actually, it's a carrot dependency, so it should be deduped.

Why does bundling on npm@2 solve problems?

[bcoe]

@jamestalmage nyc relies on a few popular dependencies that themselves use a singleton pattern (for various reasons, maintaining state, etc).

Bundling dependencies helped to solve this issue, but I found that deduping dependencies and publishing with [email protected] continued to introduce some regressions:

#246

[jamestalmage]

Hmm.

Have we figured out why that is happening? Is there a bug somewhere in npm? Ideally we wouldn't be so brittle.