Migrate to Playwright please

[suntong]

Just like this article said,

 If you thought Puppeteer was powerful, Playwright will blow your mind.

I totally agree with that, having carefully exam the differences between Puppeteer and Playwright.

Thus I'm logging a wish-list that someday Puppeteer can be migrated to Playwright.

References

• Playwright vs. Puppeteer

  If you compare the contributor pages for Playwright and Puppeteer, you’ll notice the top two contributors to Puppeteer now work on Playwright. The Puppeteer team essentially moved from Google to Microsoft and became the Playwright team. As a result, Playwright is very similar to Puppeteer in many respects. The API methods are identical in most cases, and Playwright also bundles compatible browsers by default. Because Playwright and Puppeteer were largely developed by the same team and have such similar APIs, migrating from Puppeteer to Playwright isn’t too difficult.

• Puppeteer to Playwright Migration Guide

  By following these rules we migrated all 92 test cases in CodeceptJS. Our framework is focused on end to end testing, so our code touched Playwright APIs important for testing.

[suntong]

v0.26 (Mar 4, 2021) renamed NPM package name from wechaty-puppet-puppeteer to wechaty-puppet-wechat

It's just perfect timing -- we don't even need to rename after the migration.

[huan]

Thank you very much for the suggestion!

I believe it's not too hard for us to support both, and switching between them by an environment variable.

PR will be welcome.