Skip to content

TypeScript: Migrate packages/jest-puppeteer-axe package to TypeScript #70523

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

Open
wants to merge 3 commits into
base: trunk
Choose a base branch
from

Conversation

SainathPoojary
Copy link
Contributor

@SainathPoojary SainathPoojary commented Jun 25, 2025

What?

Part of: #67691
Migrating the packages/jest-puppeteer-axe package to Typescript.

Why?

Type safety.

@t-hamano t-hamano mentioned this pull request Jun 24, 2025
27 tasks
@t-hamano t-hamano added [Type] Code Quality Issues or PRs that relate to code quality [Tool] Jest Puppeteer aXe /packages/jest-puppeteer-axe labels Jun 25, 2025
@SainathPoojary SainathPoojary changed the title [WIP]: Migrate packages/jest-puppeteer-axe package to TypeScript TypeScript: Migrate packages/jest-puppeteer-axe package to TypeScript Jun 27, 2025
@SainathPoojary SainathPoojary marked this pull request as ready for review June 27, 2025 16:08
Copy link

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: SainathPoojary <sainathpoojary@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Tool] Jest Puppeteer aXe /packages/jest-puppeteer-axe [Type] Code Quality Issues or PRs that relate to code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants