Styles Route: Reference the api-fetch and html-entities projects - #81989
Conversation
The route declares both as dependencies, and now that route projects are under the typecheck run their TypeScript config has to reference them. Validation fails for every branch until it does. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
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. |
|
Flaky tests detected in f95c4ab. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/32735289788 Should save the changes in
|
What?
Adds the two project references missing from
routes/styles/tsconfig.json:api-fetchandhtml-entities.Why?
The route declares both packages as dependencies, and since #81847 brought the route projects under the typecheck run,
npm run lint:tsconfigrequires every dependency to be matched by a reference. The styles route's config is missing these two, so the Static Analysis job currently fails on every branch, and the pre-commit hook blocks any commit that stages a tsconfig file.How?
Two lines, in the alphabetical positions the validator expects.
Testing Instructions
Exits 1 on trunk naming these two references; exits 0 with this change.
Use of AI Tools
Authored with Claude Code (Claude Fable 5), including this description; reviewed by the PR author.
Verified:
npm run lint:tsconfigexits 0 andnpx tsc -p routes/styles/tsconfig.jsonreports no errors on this branch.