-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): switch from Cypress to Playwright #5814
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
chore(website): switch from Cypress to Playwright #5814
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
LGTM - one minor comment then lets goooo
Co-authored-by: Brad Zacher <brad.zacher@gmail.com>
PR Checklist
Overview
I have failed to get Cypress running reliably in GitHub Actions (#5764). This is getting ridiculous. cypress-io/cypress#7062 is still open after two years.
Playwright, on the other hand, worked first try. And people seem to really like it. So that's that.
Note that this doesn't yet cache Playwright browsers. I think we can take that on as a followup tasks, since caching is always tricky. But I can tackle it here if you'd prefer.