Deku/playwright port

[kumardeepakr3]

Pull Request Template

Description

Please include a summary of the change or which issue is fixed. Also, include relevant motivation and context. Remember, as mentioned in the contribution guidelines that PR's should be as atomic as possible 1 feature === 1 PR. 1 bugfix === 1 PR.

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• [ ] My code follows the style guidelines of this project. npm run lint passes with no errors.
• [ ] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes. npm run test passes with no errors.

[tnolet]

@kumardeepakr3 this looks very interesting. Any reason for immediately closing the PR? We would love to make Playwright available as a part of Puppeteer Recorder.

[kumardeepakr3]

Hey @tnolet , I was just trying something for a internal hackathon project. I saw that puppeteer's extension was created by you but there is nothing that existed for playwright. I saw on Playwright's github repo too. There was an open issue pending there. So I tweaked the codegen to output code for puppeteer recorder for playwright.

I closed the PR immediately because I was intending to merge changes to my master branch rather than for the main project.

Also I see that you have plans of extending the scope of the recorder to playwright. I'll be happy to help and collaborate if needed.

[tnolet]

@kumardeepakr3 gotcha! Thanks for explaining