deps(webdriver_js_extender): update webdriver_js_extender to 2.1

[ventuno]

Following up on angular/webdriver-js-extender#21, updating webdriver-js-extender to version 2.1.0.

Making the 2 new endpoints to send custom commands to the DevTools debugger server (available since ChromeDriver version 2.30 [1]):

• /chromium/send_command;
• /chromium/send_command_and_get_result.

available for use in protractor.

@qiyigg as you already reviewed the other PR, is there any chance you could take a look at this one as well?

[1] https://chromium.googlesource.com/chromium/src/+/711de0efbb675bd2a4a28ec47c9194d8e498e600

[ventuno]

@qiyigg would it be possible to restart the circleci build? I made no real changes besides squashing two commits into one and updating the commit message to match the required format. circleci build was green last night [1] and is red now, while travis-ci build was red last night and is green now, so I'm assuming tests may be a little flaky.

[1] https://circleci.com/gh/angular/protractor/1111

[qiyigg]

rebuilt.
But the package-lock.json file change is surprising to me. Why update webdriver_js_extender from 2.0 to 2.1 will bring lots of dependency changes. Could you verify that?

[ventuno]

Thanks @qiyigg, a lot of the dependency versions in package.json are defined as ^ or ~ so when we run npm install the latest minor/patch version update will be automatically installed.
This is not directly related to updating webdriver_js_extender, rather in the last 28 days (e.g.: the last time the package.json file was changed) a lot of new versions have been released.

Does that make sense?

[1] https://github.com/angular/protractor/blob/master/package.json

[qiyigg]

No, it shouldn't. It should only updates the dependencies that are mismatched in package.json and package-lock.json as long as you just run "npm i", not "npm update".

But I found I forgot to update package-lock.json during last release. Sent another PR to do this: #4931 (You can also find it only update the mismatched dependencies).

[ventuno]

Thanks @qiyigg, I followed your instructions, let me know if this looks better to you now. I can also wait until #4931 is merged and rebase my changes after.

Also, all builds are green now :-).

[qiyigg]

@ventuno #4931 is merged.
I guess you have to revert your package-lock.json change first, then rebase, then run 'npm i'.

[ventuno]

@qiyigg rebasing had become too complicated, so made again all changes in #4934 and closing this one.