From what I know console.log()
should work without problem printing to the STDOUT of my console, when running a script.
But in my case I have NPM configured to run Jest when issuing npm test
from the shell, and any console.log()
inside the test files doesn't print anything on the screen.
I tried also to use process.stdout.write()
but still I get no custom output when running npm test
.
How am I supposed to debug stuff in my test scripts? I can't figure out if it is a problem from Node, from NPM, or from Jest. There's a Jest issue that looks similar to mine but still I cannot solve and get to output a simple string; while there rest of Jest output is echoed as usual.
Anybody experienced a similar problem?
EDIT 1:
I tried running npm test -- --runInBand
but the log doesn't appear.
Note: trying to run the command repeatedly I can sometimes see the log, but this is then overwritten/hidden by the rest of the following Jest output.
This isn't clean, but I've had luck with it, hopefully it'll help you until a fix is published: log some extra
newline
s after the log that's getting overwritten:From the linked issue since the problem is going on since years...
There is a pull request in the alpha release that is going to fix this problem. Looks like the last refining is being worked in the past few hours (see Github issue link).
However I found a solution that works for my simplest case:
npm test -- --verbose=true
and the log will magically appear!This will not fix in every case; maybe async/multi-thread/etc will still have problems (please report your experiences, so I can update the answer); for example adding a
process.exit(1)
after the log will hide it again.Trying to press
ctrl + c
before theprocess.exit()
runs (with the right timing...) will show that the log is actually there and being overridden.I will update the answer with news, but probably this will help others in starting with Node/NPM/Jest setups!