browserify / browserify/watchify

BUG: When <stdin> is closed the watcher does not terminate

Open
#336 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
1.8k
Forks
178
PR merge metrics
No merged PRs in 30d

Description

As per usual process connections when is closed a process should close unless it is designed to remain open as a daemon or persistent process, however right now when watchify is called, the hosting server manages its processes by closing the stdin file descriptor (and in this case also dying right after), but watchify keeps on running, disconnected from anything but init itself, I have to find the (in this case over 40) running instances of watchify and kill it(/them) as I dev. If the current functionality is wanted, where it stays running even when its parent process and input file descriptors die, any chance of a parameter that makes it act like a normal process then so it can be properly launched/killed by IDE's and build servers?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.