yeoman/update-notifier — pull request #37 by Bartvds (2014-06-20 16:44:07+00:00)
Title: using spawn() instead of fork()

By using a detached process a quick parent doesn't prematurely kill the slow child (which would block the update from ever being completed successfully)

From the docs of spawn():

> If the `detached` option is set, the child process will be made the leader of a new process group. This makes it possible for the child to continue running after the parent exits.

This is not the same as just calling `unref()` and `disconnect()` on a fork()

fixes #21

I've got this code in the wild for a while (as git-url dependency).

I re-tested this today: with npm version of `update-notifier` without the callback I never get an update: after resetting the `lastUpdateCheck` to zero and running the app the config the `lastUpdateCheck` gets updated but the `update` never shows up.

When I swap it for this patched version it works as expected.