Cross-tab state. Non-linear flows. The inputs nobody wants to build and everybody wants to import. Rxova ships framework-agnostic cores, React bindings where they earn their place, and APIs small enough to stay still.
Declarative journey graphs for non-linear UI flows.
Model multi-step, branching flows as a graph instead of a tangle of booleans and effects. Core is framework-agnostic; React bindings and a Chrome DevTools bridge come in the box.
npm i @rxova/journey-core
The tricky React inputs, done right.
Nine focused input components — currency, OTP, rating, password, phone, date, time, tags and file. Headless with no stylesheet to import, accessible by construction, and zero runtime dependencies each.
npm i @rxova/react-inputs
import { CurrencyInput, OtpInput } from '@rxova/react-inputs'
<CurrencyInput locale="en-US" currency="USD" value={price} onChange={setPrice} />
<OtpInput length={6} value={code} onChange={setCode} label="One-time code" />State and messages that exist in every tab, window, and worker.
Share state and messages across every tab, window, and worker — a framework-agnostic core plus React bindings, one small API.
npm i use-everywhere
import { useSharedState } from 'use-everywhere'
// No Provider. The value now exists in every tab on the origin.
const [count, setCount] = useSharedState('count', 0)Three projects, one set of rules. These are what Journey, react-inputs and use-everywhere have in common — and what they are held to.
Each library solves one problem and stops there. No plugin system, no configuration to learn before the first useful line.
Types are part of the public API, not generated as an afterthought — and the framework-agnostic core always ships apart from its React bindings.
Keyboard handling, ARIA, focus, and locale are part of the component — not an issue filed after launch.
Nothing here requires anything else here. Take one package, keep the rest of your stack exactly as it is.
Senior Frontend Engineer focused on React architecture, reusable developer infrastructure, and tools for complex user interfaces. Rxova is where I build focused open-source libraries with stable APIs, strong TypeScript support, thorough testing, and documentation that answers the question you actually arrived with.
Everything here is new and moving. Starring a repo is what tells me which of these is worth the next month of work.