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.
🐛 BUG: Devtools does not receive console logs
See original GitHub issueWhat version of Wrangler are you using?
2.0.16
What operating system are you using?
Windows
Describe the Bug
Write a basic worker which uses some console logs, and open the devtools. When it’s loaded, make a request to your worker, and observe that the logs will be shown in the terminal, but not shown on the Devtool’s console tab.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Chrome: console.log, console.debug are not working
log statements to my Javascript, and nothing was displaying in the console. Problem turned out to be due to browser caching... it wasn't...
Read more >Log messages in the Console - Chrome Developers
Learn how to log messages to the Console. ... See Get Started to explore what else you can do with DevTools. See Format...
Read more >View and save your browser console logs - Zapier Help
1. Retrieve logs for Chrome · Open the main Chrome menu · Select More Tools > Developer Tools · Depending on which logs...
Read more >754861 - console.log doesn't show objects at the time of ...
Currently the bug you are seeing happens because we store a reference to the object you evaluate and inspect it live. So any...
Read more >Use Chrome Developer Tools – Figma Help Center
Why: The Developer Console Log gives us access to a list of actions the browser has ... These do not impact performance or...
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
good catch! looks like we lost it for local mode during a refactor
On 2.0.17 this is still applicable (no logs shown) in local mode, however works as expected when using remote mode