Fix : protractor 3.x not compatible with node v0.12.x + chromedriver … #146
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
…configuration coments.
|
the Angular Team is advocating node 4+ and npm 3+ I can leave a note for people who are using older versions |
|
I added a comment to faq |
|
Hello, that's fine. |
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.
Hi,
I am currently using node v0.12.x on which protractor 3 does not work : i have to fallback to version 2.5.1.
As such, I also faced another issue with chromedriver location : so i put some comments in the protractor conf file to guide people.
I suggest this PR as fix for people who are still using this version of node.
There is actually no specific branch where i can PR, so i PR this on master.
Please let me know if you create a specific branch for me to PR.
Best regards,
Michel.