Closed bobwieler closed 3 days ago
Thanks for raising the issue. We had indeed displayed console.log-s from node modules code before, though without any location where they have been logged from. We have just added in to Wallaby 2, and are also now capturing and displaying the location as well:
Please update to the latest core v1.0.1614 to get the change.
Issue description or question
We often need to debug issues that are in libraries that we import. Any console.log statements that are in our project's code is being displayed however any console.log that we add to an imported library are not. This is something that used to work prior to Wallaby 2.0 and is incredibly important for debugging.
As an example, the following is the log output when running the tests:
What gets displayed in Wallaby's logs is:
The console.log statement with "I am inside of a library" is no longer being displayed.
Wallaby diagnostics report