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: page is not defined
See original GitHub issueWhenever I try and run I get this error
(node:5483) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): ReferenceError: page is not defined
(node:5483) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Error: Evaluation failed: ReferenceError: page is not defined ...
The code is executed in a DOM context so the page variable is not valid there. You should be calling that outside of...
Read more >ReferenceError: "x" is not defined - JavaScript - MDN Web Docs
The JavaScript exception "variable is not defined" occurs when there is a non-existent variable referenced somewhere.
Read more >ReferenceError: document is not defined in JavaScript
The "ReferenceError: document is not defined" error is thrown when the code tries to access the document object, but the object is not ......
Read more >ReferenceError: document is not defined in JavaScript
referenceerror document is not defined. The document relates to the document object which represents a web page that is loaded in the browser....
Read more >page is not defined. CRA + typescript · Issue #253 - GitHub
It looks like this has nothing to do with typescript but with react-scripts overriding the testEnvironment to 'jsdom' if --env isn't provided.
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
success! thanks. A local build with node 8.6 worked for me.
Thanks for following up! I didn’t have chromedriver on my system so I went ahead and installed it with homebrew. After that I started to get the same error you did. I was able to fix the issue for me in https://github.com/christopherwk210/site-scan/commit/20d87acf8c4e5316550f0fd9428a051cfc45270e, please update one more time and let me know if it works 👍