console errors
See original GitHub issue- On pr page
❌ pr-branches
content.js:1865 Error: GraphQL:
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
Argument 'number' on Field 'NaN' has an invalid value. Expected type 'Int!'.
- Almost all pages
❌ remove-projects-tab
content.js:1865 TypeError: Cannot read property 'parentElement' of null
at content.js:2490
at content.js:478
at remove_projects_tab_init (content.js:2501)
at async features_run (content.js:1860)
- Doesnt always give the error but it stopped working: https://github.com/sindresorhus/refined-github/issues/1940
❌ show-names
content.js:1865 TypeError: Cannot read property 'name' of undefined
at show_names_init (content.js:4586)
at async details.init (content.js:1903)
at async features_run (content.js:1860)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (8 by maintainers)
Top Results From Across the Web
How to open the browser console to view errors
How to open the browser console to view errors ; Browser Console · : - Ctrl + Shift + J (Windows/Linux) - Command...
Read more >Fix JavaScript errors that are reported in the Console
Open the demo webpage JavaScript error reported in the Console tool in a new window or tab. · Right-click anywhere in the webpage...
Read more >JavaScript console.error() Method - W3Schools
The error() method writes an error message to the console. The console is useful for testing purposes. Syntax. console.error(message). Parameters ...
Read more >Debugging Browser Console Errors - Delicious Brains
Open the Chrome developer tools (F12 / ⌘-Option-I) · Click the Console tab · Click the Clear console icon to clear the current...
Read more >Browser errors were logged to the console - Chrome Developers
# How the Lighthouse browser error audit fails. Lighthouse flags all browser errors logged to the console: Lighthouse audit showing browser ...
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 FreeTop 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
Top GitHub Comments
That’s been fixed by https://github.com/sindresorhus/refined-github/pull/1941 ✅
Yeah, I dropped the pop up because it’s options are already accessible via right click and it’s not something people actually need it that frequently. The only reason why we have a “browser_action” at all is for GHE users.