Repository navigation
v0.5.100
Upgrading
- Run
kit:update plan|applyforcore(re-pinnedsha256:df22fcbb…d4fa→sha256:b293e91e…74f4):feature.jsonaddsclass-variance-authorityandtw-animate-csstorequires.npm. No stub changes. - The dev floor for tey/standards is now
^0.11.52, the first release that reads an inventory'sfeaturesblock.
Fixed
- standards:adoption no longer reads the kit's own dependencies and host UI as gaps.
resources/adoption/surfaces.jsonnow carries a top-levelfeaturesobject: for each feature withrequires.npmorrequires.host_ui, its npm package names and its host UI primitives, exactly as itsfeature.jsonlists them. tey/standards 0.11.52 treats those packages as the kit's (never a package.json gap or a third-party import) and thosecomponents/uifiles as kit-owned (never an app component, gap or hand-rolled hit) for each installed feature. The schema allows the field, and the inventory test fails when it drifts from thefeature.jsonfiles. - core declares every npm package its components need.
Kit/Feedback/alertVariants.ts(like the shadcnbuttonit pairs with) importsclass-variance-authority, and the kit's menus, toasts and select animate withtw-animate-cssutilities (animate-in,fade-in-0,zoom-in-95); neither was inrequires.npm, so a host without them got no plan attention for it. Both are now required, at^0.7.1and^1.4.0.
What's Changed
- Declare feature npm and host UI deps in the adoption inventory (0.5.x) by @jaspertey in #463
- Release v0.5.100 by @jaspertey in #469
Full Changelog: v0.5.99...v0.5.100