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.

Element explorer doesn't work on Node 8

See original GitHub issue

Bug report

Node Version: 8.0.0
Protractor Version: 5.1.2
Angular Version: n/a
Browser(s): Chrome / chromedriver 2.29.0
Operating System and Version Mac Sierra 10.12.5
Your protractor configuration file n/a

After installing node v8.0.0 and npm v5.0.0, reinstalling protractor globally and running webdriver-manager update, I cannot run protractor --elementExplorer because I receive the following error:

protractor --elementExplorer
(node:76684) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[11:04:10] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[11:04:11] I/protractor -
[11:04:11] I/protractor - ------- Element Explorer -------
[11:04:11] I/protractor - Starting WebDriver debugger in a child process. Element Explorer is still beta, please report issues at github.com/angular/protractor
[11:04:11] I/protractor -
[11:04:11] I/protractor - Type <tab> to see a list of locator strategies.
[11:04:11] I/protractor - Use the `list` helper function to find elements by strategy:
[11:04:11] I/protractor -   e.g., list(by.binding('')) gets all bindings.
[11:04:11] I/protractor -
module.js:487
    throw err;
    ^

Error: Cannot find module '_debugger'
    at Function.Module._resolveFilename (module.js:485:15)
    at Function.Module._load (module.js:437:25)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/protractor/built/debugger/debuggerCommons.js:1:82)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)

If I revert back to node 7.10.0 I don’t get this error.

Issue Analytics

State:
Created 6 years ago
Reactions:67
Comments:65 (27 by maintainers)

Top GitHub Comments

46reactions

uriah-ascendcommented, Oct 6, 2017

Are there plans from the team to get this working again with either the inspect API or something other approach?

19reactions

bakasmariuscommented, Jul 25, 2017

Could we please know what are the plans for Node 8 support? 😃

Top Results From Across the Web

protractor elementExplorer or elementor is not working in node 8

I have upgraded from node 7 to node 8.1.2 and my element explorer stopped working with below error. normally i uses elementor or...

Use Source Control Explorer to manage files - Azure Repos

Use Source Control Explorer to browse file versions and work with your codebase under Team Foundation Version Control (TFVC).

Getting started - Bootstrap

Should you encounter problems with installing dependencies or running Grunt commands, first delete the /node_modules/ directory generated by npm. Then, rerun ...

How to Upgrade to React 18

If your app doesn't work after upgrading, check whether it's wrapped in <StrictMode> . Strict Mode has gotten stricter in React 18, ...

The 10 Most Common JavaScript Issues Developers Face

But we still wouldn't think this would be a problem, since each time through ... onClick to element.click , the circular reference is...