Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change default behavior for output piping

See original GitHub issue

Based on #19, #23,#27 it seems that the textual add-on that npm-watch does has generated a number of issues. I propose changing the default to simply be passing it along, and if the user explicitly opts-in, the script name could be pre-pended/output would be color stripped. This allows us to inform the user that the opt-in modes may produce have unpleasant visual effects that are not in our control due to I/O issues.

Tagging @alxndr , @hectormenendez , @domarmstrong, @duivv for feedback as they have been involved in issues/prs related to this issue.

Issue Analytics

State:
Created 7 years ago
Reactions:3
Comments:11 (5 by maintainers)

Top GitHub Comments

3reactions

M-Zubercommented, Jul 30, 2021

New version is out: https://www.npmjs.com/package/npm-watch/v/0.11.0

1reaction

mashaalmemoncommented, Jul 12, 2021

@M-Zuber , would the change from @leviwheatcroft be able to be made in master? We’re experiencing log message styles/colors not making their way properly through when npm-watching the process. If inherit was set to ['pipe', 'inherit', 'inherit'] we would be all set.

Could submit a PR if it made things easier. Literally a 1 parameter change.