Looks like Appveyor is broken.

@sokra – you mentioned that this feature was PR worthy in #1308, though I'm not sure if it's testable as it's using process.
I can't find any tests for the other process listeners in bin/webpack.js (here), so I'm not sure where to try adding tests for this.

Totally realize that this is probably an edge-case, but I'm happy to do the work to get it merged in, just need a bit of direction. Thanks!

yeah, there are no automatic tests for the CLI yet. You can goto webpack/test/browsertest and run node build.js. This uses the CLI. Then open tests.html for the browsertests.

So, I'm opening the node process with the ErlangVM and when stdin closes, it's shutting down. Without my patch, the process is never closed.

I just want to know what to do to get this merged

Not sure... I'm not so much into these OS internals to decide if this is fine. Would love to see more feedback about the fix. It's pretty radical and if wrong it would break stuff..

The same change to brunch broke running it as a background process (brunch/brunch#998). From that discussion, they're going to make this behaviour opt-in through --stdin.

👍 for this change, it is fairly common behaviour, but I would also follow @jjt advice of only checking stdin if a flag (for example, --stdin) is set.

I'm just the messenger :)

@matthewlehner Do you want to update the PR to reflect @jjt and @josevalim ideas? And please rebase it to fix the CI bugs.

👍 I'm on it.

@sokra I've just implemented these changes with --watch-stdin as the new option.

I've rebased to master, but CI bugs still seem to be here.

The CI build fails because of incorrect code formating. Run npm test to see the results. Or run npm run beautify to fix it.

@sokra Ah ha, sorry about that. Everything passes now. 👍

Just checking if there's anything I can do to help move this along? Appveyor still seems broken for some reason..

@sokra Just rebased to master and everything passes. Is there anything else I need to do to get this merged?

Thanks