You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Check the split @wordpress/theme versions and scaffold requirements against wp-scripts 37 #79
package-lock.json now carries three @wordpress/theme versions: 4.0.0 at the top level (the @wordpress/stylelint-config peer), 3.0.0 under @wordpress/server-side-render, and 2.3.0 under the editor packages (commands, notices, preferences, ui, image-cropper) and @wordpress/eslint-plugin. Builds and lint pass today, but nobody has checked that the mixed design-token versions behave the same in the editor.
Aditya also flagged the older scaffold requirements as worth a compatibility check against the new dependency set.
To do:
Check whether the editor packages pin @wordpress/theme 2.3.0 on purpose or only lag behind, and whether the next WordPress package release lines them up.
Run the block and scaffold flows (npm run init, npx wp-tooling add, npm run start:blocks) against the 37 toolchain and note anything that breaks or warns.
Drop the direct @wordpress/theme entry once a clean install hoists a version the Stylelint config accepts.
Activity