ContractSpec
ContractSpecOpen spec system
Menu

Choose your entry point

ProductTemplatesPricingDocsChangelogGitHub
Start with OSSExplore Studio
Back to changelog index

0.1.6

May 25, 2026 · 2 packages · 4 unique changes · 2 release entries

libs

This release affects the sharedLibs family.

Run contractspec connect adoption resolve --family sharedLibs to see how it impacts your project.

Release summaries

  • m2-cockpit-kit

    Additive: M2 new lib @lssm-tech/lib.cockpit-kit (native lane + shared types) for cross-OS cockpit composites; ships canonical Density + Expansion variant unions and 4 primitive prop interfaces (Phase 0 scaffold).

    maintainer

    New native-lane package paired with @lssm-tech/lib.cockpit-kit-web. Owns the canonical Density ('comfortable' | 'compact') and Expansion ('collapsed' | 'expanded') literal union vocabulary used by lib.personalized-presentation. Phase 0 ships type contracts only — CockpitFrame, NavRail, GraphCanvas, MetricPanel implementations land in Phase 1 after the Phase 0.5 shape survey resolves API divergence escalations.

    integrator

    For new cockpit-class UI work, prefer importing primitive prop interfaces from @lssm-tech/lib.cockpit-kit/types. Density / Expansion literal types live under @lssm-tech/lib.cockpit-kit/variants. Do NOT redefine these unions in your own package — always import from cockpit-kit so the personalization spine and cockpit primitives stay structurally aligned.

  • m2-cockpit-kit-web

    Additive: M2 new lib @lssm-tech/lib.cockpit-kit-web (web lane) paired with lib.cockpit-kit; re-exports canonical variant unions and primitive prop types via metro+turbopack aliases (Phase 0 scaffold).

    maintainer

    Web-lane mirror of @lssm-tech/lib.cockpit-kit. Pairs with the native package via withPresentationTurbopackAliases (Next) and withPresentationMetroAliases (Expo/Metro) — native consumers automatically resolve cockpit-kit-web/ui/* to cockpit-kit/ui/* per platform. The package re-exports the canonical Density + Expansion variant unions from cockpit-kit; no local redefinition (single source of truth lives in cockpit-kit).

    integrator

    For Next.js / web apps, ensure withPresentationTurbopackAliases (or withPresentationWebpackAliases) is called in your next.config so that cockpit-kit-web resolves correctly. For Expo / React Native apps, ensure withPresentationMetroAliases is called in your metro.config to flip cockpit-kit-web/ui/* to cockpit-kit/ui/* on native platforms.

Upgrade steps

  • Register cockpit-kit aliases in next.config / metro.config

    assisted

    The presentation-runtime-core helpers gained cockpitKit / cockpitKitWeb options with safe defaults. New web apps need no extra wiring beyond calling the helper.

    Packages: @lssm-tech/lib.cockpit-kit-web

    1. Next.js: wrap nextConfig via withPresentationTurbopackAliases — defaults register @lssm-tech/lib.cockpit-kit ↔ @lssm-tech/lib.cockpit-kit-web automatically.
    2. Expo/Metro: wrap metro config via withPresentationMetroAliases — defaults handle the cockpit-kit-web/ui/* → cockpit-kit/ui/* native flip.

  • Import Density / Expansion from cockpit-kit

    assisted

    cockpit-kit owns the canonical variant vocabulary. Personalization-aware components should import the literal unions from cockpit-kit, not redeclare them.

    Packages: @lssm-tech/lib.cockpit-kit

    1. Import: `import type { Density, Expansion } from '@lssm-tech/lib.cockpit-kit/variants'`
    2. Use the literal-union types as cva variant prop names for density+expansion-aware components.

Unique release changes

  • - Additive: M2 new lib @lssm-tech/lib.cockpit-kit (native lane + shared types) for cross-OS cockpit composites; ships canonical Density + Expansion variant unions and 4 primitive prop interfaces (Phase 0 scaffold).

    1 packages · 1 occurrences

  • - Additive: M2 new lib @lssm-tech/lib.cockpit-kit-web (web lane) paired with lib.cockpit-kit; re-exports canonical variant unions and primitive prop types via metro+turbopack aliases (Phase 0 scaffold).

    1 packages · 1 occurrences

  • - cockpit-kit owns the canonical variant vocabulary. Personalization-aware components should import the literal unions from cockpit-kit, not redeclare them.

    1 packages · 1 occurrences

  • - The presentation-runtime-core helpers gained cockpitKit / cockpitKitWeb options with safe defaults. New web apps need no extra wiring beyond calling the helper.

    1 packages · 1 occurrences

Impacted packages

  • @lssm-tech/lib.cockpit-kit

    Layer: libs · 2 changes

  • @lssm-tech/lib.cockpit-kit-web

    Layer: libs · 2 changes