Do you have `Cannot read property 'addEventListener' of undefined`?
See original GitHub issue- Version (
cloudcmd -v
): at least since v11.1.0 - Node Version
node -v
: v8.11.4 - Browser name/version: Chrome 68
- Used Command Line Parameters: (no arguments)
Just run cloudcmd
without any arguments and open the page. The devtool shows:
Uncaught (in promise) TypeError: Cannot read property 'addEventListener' of undefined
at cloudcmd.js:68
at Generator.next (<anonymous>)
at n (key.js:79)
at u (key.js:79)
Not sure whether this has any impact, but do you have this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Cannot read property 'addEventListener' of null - Stack Overflow
I think the easiest approach would be to just check that el is not null before adding an event listener: var el =...
Read more >Uncaught TypeError cannot read property 'addeventlistener' of ...
In JavaScript, a very common error is the Uncaught TypeError Cannot read property 'addeventlistener' of null. This error occurs when JavaScript is not...
Read more >[SOLVED] Cannot Read Property 'addEventListener' of Null in ...
To fix the “cannot read property 'addEventListener' of null” error, make sure the selector used the access the element is properly defined.
Read more >Cannot read property 'addEventListener' of undefined?
When I pressed a button to clear the content in the textarea, the console log gives me an error. Uncaught TypeError: Cannot read...
Read more >Cannot read property 'addEventListener' of null - JavaScript
Hi Fellow learners I got this issue that I can't get passed. Tried to google it and searched on StackOverflow but still stuck....
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
Fixed with b782c0a, landed in v11.7.1 🎉
I understood what are you talking about. I didn’t test this case for a long time, just tried it and I managed to reproduce this bug, thank you for explanation 😃.