Skip to content

Conversation

@darrenjennings
Copy link
Contributor

The yarn.lock file changes fairly drastically when I run yarn so not committing it in this PR. I was able to run the test and it ran successfully. I also ran this in the context of a new project and everything seems to work well with boilerplate generators.

$ yarn -v
1.13.0

image

@darrenjennings
Copy link
Contributor Author

@sodatea you may also want to bump chromedriver for the next major release since it has been bumped a couple major versions. Chrome is at version 74 and this chromedriver expects versions 70-73.

@haoqunjiang
Copy link
Member

So now chromedriver's major version number is strictly in line with Chrome, whose release cycle is 6 weeks? In that case I think we'll need to hoist the chromedriver dependency to project root.

@darrenjennings darrenjennings deleted the chore/nightwatch-plugin-bump-version branch August 8, 2019 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants