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.
Console log test messages should be removed.
See original GitHub issueThere are some console.log('test') messages that should be removed, because those are popping out in our site.
There are some logs like this on slick.js:
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
Should I be removing console.log from production code?
Yes. console.log will throw an exception in browsers that don't have support for it (console object ...
Read more >Jest eats up all console.log messages during debugging #8208
Currently Jest eats up all console.log/warn/error messages during debugging and I'm completely blind all the way through up until the test ...
Read more >Ways to Remove Those Pesky console.log Statements
The lowest tech solution is to go through your code-base and manually remove all instances of console statements. This includes variations such ...
Read more >Hide all console logs in production with just 3 lines of code
We basically use the console.log() in our JS application to check wether our code is working properly or to replicate the bug or...
Read more >Log messages in the Console - Chrome Developers
Click the Log Levels drop-down and disable Errors. A level is disabled when there is no longer a checkmark next to it. The...
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
Fix merged into master, will be in the next minor release
Is it planned to remove the console.log messages also from the npm package?