-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Introduce React Scanner for component usage stats #65463
base: trunk
Are you sure you want to change the base?
Conversation
Size Change: 0 B Total Size: 1.81 MB ℹ️ View Unchanged
|
6ecd093
to
78cd111
Compare
78cd111
to
4116e4e
Compare
Flaky tests detected in 4116e4e. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11442534342
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
4116e4e
to
311ef37
Compare
What?
This PR introduces
react-scanner
to keep an eye on component usage stats.Why?
It can be useful to track the adoption of our components over time.
How?
Running
react-scanner
with the default config to count components and props yields a result like this:Testing Instructions
npm install
npm run component-usage-stats
Testing Instructions for Keyboard
Same
Screenshots or screencast
None