New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Output not shown in certain cases #15

Open

ghost opened this issue Mar 22, 2016 · 0 comments

ghost commented Mar 22, 2016

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

> [email protected] 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

> [email protected] 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`

> [email protected] test /Users/user/projects/test-config
> faucet

^C

$ npm run test-auto2

> [email protected] test-auto2 /Users/user/projects/test-config
> fsmonitor -s npm test


Monitoring:  ~/projects/test-config
    filter:  **/
    action:  npm test

npm test

> [email protected] 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment