This repo is to replicate how a project works when winston is used for logging and jest at master. I believe this is a regression because [email protected] works with this setup.
It seems that there's a bug in BufferedConsole in jest-util
. Internally, winston uses console._stdout.write
when you log. I don't have enough context on how jest overrides the global console object but I know jest does this so that it can defer logging in getConsoleOutput
.
With [email protected]
- Run yarn to install deps
- Run
yarn test
- Verify tests pass
With jest@master
- Build jest locally
- cd into
jest/packages/jest-cli
in your local version of jest and runyarn link
- cd back into this project and run
yarn link jest-cli
- Run
yarn test
- Verify tests fail