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.
ReferenceError: browser is not defined - Nightwatch
See original GitHub issueI´ve upgraded Nightwatch from v9.0 to v9.4 and now i´m getting this error!!! What´s causing this? Can someone please help me??
ReferenceError: browser is not defined
Issue Analytics
- State:
- Created 7 years ago
- Comments:12
Top Results From Across the Web
ReferenceError: browser is not defined - Stack Overflow
I am running this piece of code and the firefox is giving error. Uncaught ReferenceError: browser is not defined.
Read more >ReferenceError: browser is not defined - Ionic React
I am having a problem with the Chrome browser and not Firefox. Paused on exception ReferenceError: browser is not defined.
Read more >Unable to run a test in chrome browser. - Google Groups
I have just started node.js and wrote a simple script and was able to execute it in firefox and trying to run it...
Read more >ReferenceError: browser is not defined - General - Ember.JS
Hey guys, i am unable to get this to work. any idea what i need to do? I am trying to integrate web3...
Read more >How to solve the document is not defined error - Flavio Copes
Here's how to fix the “referenceerror: document is not defined” error that ... document is an object that's made available by the 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 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
No worries at all. At least now you know in future to look in the error message for which specific file is causing the issue, which will often take you directly to a syntax error or some other error.
Hmm, I haven’t used Windows in years, but I assume you’re calling nightwatch with something like:
node nightwatch.js?If so, does appending
--verbosenot work for you:node nightwatch.js --verboseThe error you posted above suggests you’ve typed
--verboseinto command prompt on its own.