For initial log statement, JEST_STARE_LOG setting seems to be ignored
See original GitHub issueRegardless of how JEST_STARE_LOG is set, the onRunStart log seems to be printed out:
jest-stare will write each completed run to <JEST_STARE_DIRECTORY>
It appears to be coming from this line of code: https://github.com/dkelosky/jest-stare/blob/master/src/reporter/Reporter.ts#L52
An additional statement that comes AFTER jest runs, does seem to be successfully suppressed, so not sure why this one is not.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How do I access my Club Jetstar account?
Log in to your account using your email address and the password you chose when you joined. We don't use membership numbers —...
Read more >How to get a copy of your itinerary - Jetstar
Once you're in manage booking, you can find the 'Resend itinerary' button under your flight details. Alternatively, you can use your first name,...
Read more >Accessing your Club Jetstar account
Information on how to log in to your Club Jetstar member account using your email and password, with links to further Club Jetstar...
Read more >Contact us | Jetstar
Contact Customer Service · New bookings · Delayed, cancelled or rescheduled flights · Change or cancel a booking · Lost, damaged and delayed...
Read more >Travel to and from the US - Jetstar
Additional requirements for 2022 travel. Visa Waiver Program (ESTA). Secure Flight and Advance Passenger Information. Passengers with a disability.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nope - the bug occurs in that version 😄 . I’ll see if I can get this fixed over the weekend. Thanks for reporting
Thanks! 1.13.1 should be published now.
Take care,