Repository navigation
Upgrade frontend tooling and adopt shared flat lint configs - #776
Merged
Merged
Conversation
obenland
force-pushed
the
chore/frontend-tooling
branch
from
September 17, 2026 13:18
40a06f6 to
001c862
Compare
obenland
marked this pull request as ready for review
September 17, 2026 13:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This follow-up upgrades Node.js from 20 to 24,
@wordpress/scriptsfrom 27.9.0 to 35.0.0, and@wordpress/envfrom 9.3.0 to 11.15.0 so the repository can use the shared flat ESLint and Stylelint configurations from wporg-repo-tools.Stacked on #775. This PR targets
chore/phpcs-toolingto show only the frontend changes; retarget it totrunkafter #775 merges. Do not merge this PR into the temporary base branch.package.jsoninto a shared-config wrapper using the CSS preset for PostCSS sources. Preserve the existing line-length and duplicate-selector exceptions, and track.stylelintrcas the entry point for both CLI and editor autodiscovery.Validation: clean
npm ci; Composer validation; PHPCS across 83 files with no errors or warnings; CSS lint; JS lint with zero errors and ten existing React Hook warnings; production build with the same 139 output paths; and PHP 8.2 tests in an isolated wp-env environment (32 tests, 107 assertions). Browser behavior has not been manually tested.