Product Decisions This Supports

Feature delivery: v2.3.0 makes dark mode a ready-to-ship capability: setMode('light' | 'dark' | 'system'), persisted choice in localStorage, live prefers-color-scheme behavior, and Bootstrap 5.3 alignment via data-bs-theme.
Roadmap: Dark mode and theme-system work can move from “custom build” to “package adoption,” freeing roadmap capacity for product features rather than UI plumbing.
Build vs buy: The package now owns dark-mode tokens, Tailwind theme wiring, component dark variants, and an AA contrast check for dark text pairs. That is a meaningful maintenance reduction versus maintaining a bespoke theme layer.
Theming and white-label use cases: The Tailwind theme now reads --rnx-* tokens, so multi-brand or tenant-specific theming can be handled by overriding CSS variables instead of forking Tailwind config or component styles.
Accessibility decisions: The release includes automated checks that dark tokens override every colour the Tailwind theme reads and that text pairs reach AA. This supports accessibility commitments in internal tools, dashboards, and customer-facing admin surfaces.
Migration risk to plan for: Teams that remap colors.indigo in Tailwind config will no longer affect the theme; they must set --rnx-* tokens instead. Tints, hover fills, and focus rings use color-mix(), so older browsers lose those visual treatments.

When to Consider This Package

Consider it when the product is a Laravel/PHP application using Tailwind and/or Bootstrap 5.3 and needs dark mode, system-preference support, and token-based theming without building those layers internally.
Strong fit for admin dashboards, internal tools, and component-heavy UIs that use elements such as Toast, StatCard, TopAppBar, modals, drawers, checkboxes, and radios.
Strong fit when accessibility matters and the team values package-level contrast checks over ad hoc dark-theme QA.
Adopt with a migration plan if the team currently customizes the theme through Tailwind colour remapping; the new contract is CSS token overrides.
Look elsewhere if the product must support browsers without color-mix() — Chrome 111, Safari 16.2, and Firefox 113 are the stated baseline — or if the design system requires Tailwind config colour remapping as the primary theming API.
Look elsewhere if the team needs a fully headless component library or a theming system independent of Bootstrap/Tailwind conventions.

For executives: v2.3.0 adds production-ready dark mode, follows system preferences, persists user choice, and aligns with Bootstrap 5.3. It also adds AA-focused dark-token checks, reducing custom theme and accessibility effort. The main caveats are a token migration for teams that customize Tailwind colours and a modern-browser baseline for some visual effects.
For engineering: The package exposes a small mode API, sets data-mode and data-bs-theme, persists to localStorage, and reacts to prefers-color-scheme. The Tailwind theme now reads --rnx-* tokens with existing hex fallbacks, so default appearance is unchanged. Existing Tailwind colour remaps will stop affecting the theme; migrate to token overrides. Also note color-mix() support requirements for tints, hover fills, and focus rings, plus fixes for toast dark styling and Tailwind class generation in Toast, StatCard, and TopAppBar.