I've found two different cases where the output of faucet is mysteriously missing:
- webstorm npm integration
- executing a task through the npm tool window shows other output to stdout but not from faucet
- nodemon, example shown below
package.json:
"scripts": {
"test": "faucet",
"test-auto": "nodemon --exec 'npm test'",
"test-auto2": "fsmonitor -s npm test"
}
cli:
$ npm test
> test-config@1.0.0 test /Users/user/projects/test-config
> faucet
✓ getGlobalConfig returns default when process.env is not set
# tests 2
# pass 2
✓ ok
$ npm run test-auto
> test-config@1.0.0 test-auto /Users/user/projects/test-config
> nodemon --exec 'npm test'
[nodemon] 1.9.1
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `npm test`
> test-config@1.0.0 test /Users/user/projects/test-config
> faucet
^C
$ npm run test-auto2
> test-config@1.0.0 test-auto2 /Users/user/projects/test-config
> fsmonitor -s npm test
Monitoring: ~/projects/test-config
filter: **/
action: npm test
npm test
> test-config@1.0.0 test /Users/user/projects/test-config
> faucet
✓ getGlobalConfig returns default when process.env is not set
# tests 2
# pass 2
✓ ok
......
I initially created an issue with nodemon, but it was suggested that the issue could be with how faucet is detecting the stdout stream.
I've found two different cases where the output of faucet is mysteriously missing:
package.json:
cli:
I initially created an issue with nodemon, but it was suggested that the issue could be with how faucet is detecting the stdout stream.