Framework support
Inkline supports seven frameworks. All seven get the same eight components, the same props and the same headless layer. Five are first-class with no caveats; two have differences worth knowing before you start, listed here rather than discovered later.
Support matrix
| Framework | Package | Peer dependency | Output | Bundled CSS | Caveats |
|---|---|---|---|---|---|
| React | @inkline/react | react >= 18 | TSX, hooks | Yes | — |
| Vue | @inkline/vue | vue >= 3 | SFC, <script setup> | Yes | — |
| Svelte | @inkline/svelte | svelte >= 5 | .svelte, runes | Yes | — |
| Solid | @inkline/solid | solid-js >= 1 | TSX, signals | Yes | — |
| Astro | @inkline/astro | astro ^7 | .astro | Yes | Static-first; no transition animations |
| Angular | @inkline/angular | @angular/core ^22 | Standalone components | No | No /css entry point; no transition animations |
| Qwik | @inkline/qwik | @qwik.dev/core 2.0.0-beta.47 | Qwik components | No | No /css entry point |
Every package also ships @styleframe/runtime as its single runtime dependency.
What every package exports
Three entry points, identical across all seven:
| Entry point | Contents |
|---|---|
@inkline/<framework> | The eight styled components: IBadge, IButton, ICheckbox, IFieldGroup, IHamburgerMenu, IInput, IRadioGroup, ISwitch. |
@inkline/<framework>/headless | The unstyled parts they compose — IButtonBase, IInputControlBase, ISwitchLabelBase and the rest. |
@inkline/<framework>/css | The default theme stylesheet. Not present on Angular or Qwik. |
Per-target notes
Angular
Components are standalone, so you add them to a component's imports array
rather than declaring a module:
import { IButton } from "@inkline/angular";
@Component({
standalone: true,
imports: [IButton],
template: `<uf-i-button label="Save" color="primary" />`,
})
Selectors are the component's name in kebab case with a uf- prefix:
uf-i-button, uf-i-input, uf-i-switch. Props are Angular signal inputs and
use the same names as everywhere else, class and style included: a class on
the host lands on the component's root element.
Two differences to plan for:
- No
/cssentry point. The package ships no bundled stylesheet. Generate one from astyleframe.config.tsand add it to thestylesarray inangular.json— see Theming. - No transition animations. Where other targets emit a real transition wrapper, Angular receives the element unwrapped with the transition classes applied. Components appear and disappear correctly; they do not animate unless you wire up Angular's own animation system.
Astro
Components render at build time and ship no JavaScript, which is what you want from Astro — and it means anything interactive needs a client directive or an island in another framework.
- No transition animations, for the same reason as Angular: the transition wrapper is unwrapped and only the classes remain. There is no runtime to drive the animation.
React, Vue, Svelte, Solid, Qwik
No caveats on the component surface: transitions animate, props behave as documented, and the headless layer is complete.
Qwik is first-class in every respect except one — like Angular, it ships no
/css entry point, so you build the stylesheet from a styleframe.config.ts
and import it from your root component.
Choosing between packages
You install exactly one. If your app is a single framework, that is the whole decision.
If you run several — a React product and a Vue admin panel, say — install both
packages and share one styleframe.config.ts between them. The components
consume the same tokens in every framework, so one theme file keeps two apps
visually identical. That is the case Inkline is built for.
Next steps
- Installation — the command for your framework.
- Theming — the shared config file referenced above.