New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
devtools: fix import of devices #5369
devtools: fix import of devices #5369
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am curious if one of the test should have failed in cases this import fails.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh, there we go. I guess the actual problem was that Puppeteer updated with a breaking change which users picked up automatically.
Same errors occurs with To make devtools |
Can confirm what @vitalyiegorov noted, this change breaks our test suite |
@vitalyiegorov @lg-kialo I can't reproduce the issue. Would you mind to clean up const DevTools = require('devtools').default
;(async() => {
const client = await DevTools.newSession({
capabilities: { browserName: 'chrome' }
})
await client.navigateTo('https://www.google.com/ncr')
console.log(await client.getTitle())
await client.deleteSession()
})() |
I did that and it fixed it, not sure what the issue was. Could be that puppeteer was on an older version. Thanks! |
@christian-bromann Tried, but the issue is still here, I have investigated the versions of the packages and it resolves to If you will take a look at the master version of puppeteer-core it has the same behavior, so I guess you should update the import of |
@vitalyiegorov please update your packages, your puppeteer-core version should be at |
Proposed changes
Fixes #5368
Types of changes
Checklist
Reviewers: @webdriverio/project-committers