Incompatibility with node 8 #4345
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
June 20, 2017 14:09
|
@heathkit and @NickTomlin What do you think about this PR for the current NodeJS 8 support? |
|
Do we also have other compatibility issues besides protractor debugger/explorer? |
|
We only have compatibility issues with debugger and we don't want to use that debugger after node 8. We already had doc to show how to use chrome debugger and also explain the previous debugger was deprecated in node 8; therefore close this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing the element explorer with node8 won't be trivial - until then it worth to mention in the readme that protractor not working with the newest node version well.
#4307