Slider
Free · MITHeadless, accessible, and styled entirely through the attribute surface below — bring your own CSS system, or start from the reference theme.
Install
Without a flag you get no styling at all — plain HTML carrying the attribute surface below. --theme copies the same theme in two dialects;--bridge lumos re-points either one onto Lumos for Astro's tokens (it needs a theme to re-point, and Lumos itself, already in your project).
Unstyled — behavior only, you write the CSS
npx astrocraft-ui add forms/sliderPlain-CSS theme — no build step
npx astrocraft-ui add forms/slider --theme cssTailwind theme — needs Tailwind v4
npx astrocraft-ui add forms/slider --theme tailwindPlain-CSS theme, re-pointed onto Lumos tokens
npx astrocraft-ui add forms/slider --theme css --bridge lumosTailwind theme, re-pointed onto Lumos tokens
npx astrocraft-ui add forms/slider --theme tailwind --bridge lumosLive demo
Slider
Attribute surface
With no class-merging machinery, these attributes are the whole extension point. State is a data-attribute or a native attribute; visibility is the hiddenattribute. Generated from source by pnpm slots.
| Component | Slots | Variants | Runtime state | Native state |
|---|---|---|---|---|
| `Slider.astro` | `slider` | `data-size`: `sm` · `md` | — | — |
Source
What the command copies — 2 files, alias-free so the copy lands standing alone. This is the whole component, shown without its comments; the files you install keep them, with the reasoning behind every rule.
---
import type { HTMLAttributes } from "astro/types";
type Props = HTMLAttributes<"input"> & { size?: "sm" | "md" };
const { size = "md", class: className, ...rest } = Astro.props;
---
<input type="range" class={className} data-slot="slider" data-size={size} {...rest} />
import Slider from "./Slider.astro";
export { Slider };
export default Slider;
What you get
The component source, copied into your project by npx astrocraft-ui add forms/slider — no package dependency, no CSS to fight. Whatever the paid blocks compose, this is it.