Components
Forms & Input
Slider

Slider

Use Slider to build consistent, accessible interfaces aligned with the shared design system.

Installation

1. Copy the source code:

  • Source in this monorepo: packages/ui/src/components/slider.tsx
  • Place in your project: components/ui/slider.tsx
  • Required utility: lib/utils.ts (for cn helper)

2. Update the import paths to match your project structure.


Usage

import { Slider } from "@hoag/ui/components/slider";
 
export default function Demo() {
  return (
    <div className="w-80 space-y-2">
      <div className="flex items-center justify-between text-sm">
        <span>Volume</span>
        <span className="text-muted-foreground">40%</span>
      </div>
      <Slider defaultValue={[40]} max={100} step={1} />
    </div>
  );
}

Import

import { Slider } from "@hoag/ui/components/slider";

Basic Example

Volume40%
import { Slider } from "@hoag/ui/components/slider";
 
export function SliderBasicExample() {
  return (
    <div className="w-80 space-y-2">
      <div className="flex items-center justify-between text-sm">
        <span>Volume</span>
        <span className="text-muted-foreground">40%</span>
      </div>
      <Slider defaultValue={[40]} max={100} step={1} />
    </div>
  );
}

Composition Pattern

import { Slider } from "@hoag/ui/components/slider";
 
export function SliderSection() {
  return (
    <section className="space-y-3">
      <h3 className="text-sm font-medium">Slider section</h3>
      <Slider />
    </section>
  );
}

Accessibility Checklist

  • Verify semantic roles and ARIA attributes for interactive behavior.
  • Keep keyboard navigation and focus visibility consistent in all states.
  • Ensure color contrast meets accessibility requirements in light and dark themes.
  • Provide screen reader context for dynamic state or content changes.

Testing Checklist

  • Add render tests for default and key variant states.
  • Add interaction tests for callbacks and state transitions.
  • Add visual regression checks for responsive and theme variations.
  • Cover edge states such as loading, empty, disabled, and error.

Production Tips

  • Wrap component logic in feature-level abstractions for domain behavior.
  • Keep visual variants centralized to avoid style drift across screens.
  • Reuse a single import path strategy for simpler refactors.
  • Mirror documented states in Storybook and QA checklists.

Named Exports

  • Slider

API Reference

For authoritative prop signatures and implementation details, inspect:

  • packages/ui/src/components/slider.tsx

MIT 2026 © @hoag/ui