Conversation
🦋 Changeset detectedLatest commit: 034cda4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@chriseagle so this branch and #958 which is a superset of this branch are the first step imo. Remove any extra dependencies not core to the library ie: linaria, vanilla extract, storybook Update all packages to their latest stable minor #958 takes some larger important steps. Moves us off of 10up-toolkit to WP-Vite-plugins and updates Next to v16. Still keeping everything on React 18.3 to support the Pages Router but this basically does everything but upgrade to React 19 which to me is the first logical step as we'd still support everything and then have the packages in an updated spot to go to 19 and the focus is exclusively on 19 upgrades |
…nsumers The theme was a private, unpublished dev fixture that nothing depended on, but it declared 19 @wordpress/* packages at exact versions while importing only three (i18n, blocks, block-editor). Those 16 unused pins dictated dependency resolution for the entire monorepo: @wordpress/editor@14.40.2 pulled core-data@7.40.2 -> block-editor@15.13.2 -> dataviews@12.0.1, whose private-API opt-in is rejected by @wordpress/private-apis >= 1.54.0. That is what broke @headstartwp/block-primitives' test suite. WordPress packages now live only where they are imported. block-primitives already declares exactly the four it uses (block-editor, components, data, blob) and resolves them on the current generation, where dataviews no longer depends on private-apis at all. - remove wp/10up-theme and its dev:primitives turbo filter - drop the now-unnecessary @wordpress/private-apis override - repoint the staged phpcs hook at wp/headless-wp, which is where 10up/phpcs-composer actually lives; the theme had no phpcs at all - stop mounting the theme in wp/headless-wp/.wp-env.json - declare @types/react, @types/react-dom and @types/jest at the root so the root tsconfig's typeRoots and Next's own type resolution do not depend on npm hoisting happening to place them there Lockfile drops from 1975 to 1482 packages; @WordPress entries from 452 to 76. React stays on 18.3.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VMatBaQUrPS9AhSJmkF2vF
1 participant
Description of the Change
Closes #
How to test the Change
Changelog Entry
Credits
Props @username, ...
Checklist: