Closed terencechow closed 7 years ago
O_o
I can't imagine. It's been a long time since I looked at the source to this, but I use it daily. And all this does is write colored output to stdout.
I'll close this issue. Not sure what the issue was but I moved away from nodemon in favour of pm2 anyways
This is extremely odd and I don't understand the correlation. However I have a project that uses nodemon in development in a docker container. Changes that are done on the host are copied over to the container with
docker cp
. This triggers theinotify
event required to triggernodemon
to restart. Everything was working fine until I addedbunyan-debug-stream
.When I added
bunyan debug stream
,nodemon
stopped restarting due to file changes. Specifically all I added was the streams array to my log:So I must ask, what can
bunyanDebugStream
possibly be doing that prevents nodemon from restarting in a docker container? Keep in mind when I run my app locally, even withbunyanDebugStream
, it restarts fine on file changes.