Frameworks

Sometic keeps one behavior model and ships framework-native adapters on top. Prefer Wave A for production UI. Wave B and Wave C are Experimental contract surfaces, not full component kits.

Wave A (full adapters)

Production beta surface for interactive UI, forms, overlays, store binding, auth, and HTTP helpers.

GuidePackageRole
Vanilla / Web Components@sometic/elements (+ @sometic/dom)sometic-* custom elements and DOM engines
React@sometic/reactNative React components and hooks
Vue@sometic/vueNative Vue components and composables

Wave B (Experimental)

Store-bind foundations only. No button / input / form / overlay kits in these packages yet.

GuidePackageCapabilities
Angular@sometic/angularstoreBind
Svelte@sometic/sveltestoreBind
Solid@sometic/solidstoreBind
Preact@sometic/preactstoreBind

Wave C (Experimental)

HTML-first / legacy hosts. Claimed surface is storeBind plus lifecycle-safe button bind.

GuidePackageCapabilities
Alpine.js@sometic/alpinestoreBind, button
jQuery@sometic/jquerystoreBind, button
HTMX@sometic/htmxstoreBind, button

How to choose

  • Need React or Vue UI today → Wave A package + components.
  • Need custom elements or no framework → Vanilla.
  • Need store semantics in Angular / Svelte / Solid / Preact → Wave B create*StoreBind, compose with your own UI or Elements.
  • Need Alpine / jQuery / HTMX button behavior without a SPA kit → Wave C.

Maturity labels live in Beta maturity. Capability matrix: Compatibility.