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.
Log 404s to console
See original GitHub issueThe kit currently swallows 404 errors.
We should either not swallow them, or else print them to the console.
Something like console.log('404:' + err) on line 161 of lib/utils.js could work.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Log 404s to console · Issue #417 · alphagov/govuk-prototype-kit
The kit currently swallows 404 errors. We should either not swallow them, or else print them to the console. Something like console.log('404:' + ......
Read more >Can I prevent the Chrome Developer Tools console from ...
The Chrome Developer Tools console logs an error each time a page asset (including an image) isn't found (i.e. returns 404). In my...
Read more >How To Find 404 Error Pages using Google Search Console
To find the list of all 404 pages, you can log in to the Google search console account. Go to your Website dashboard...
Read more >How to Find and Fix a 404 Error on Your Website
1. Google Search Console: You will find a list of all 404 pages by logging into your Google search console account and going...
Read more >How to Find 404 Errors on Your Website | Pouch Marketing
After logging in to Google Search Console, 404s can be seen under the “Coverage” report. Click on “Excluded” and look for errors with...
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
Yes to @joelanman’s suggestion. Though could you say ‘could not’ instead of ‘couldn’t’. I know our current position is that contractions are OK. but I think the proximity to the opening quotation here might make it easier to miss.
As referenced in the closed issue, this has now been fixed, thanks everyone.
https://github.com/alphagov/govuk-prototype-kit/pull/566