About Rxova
Small libraries for the hard parts of the browser.
Built in the open by one engineer. Independent packages, one standard for finished.
- projects
- 4
- third-party deps
- 0
- maintainer
- 1
Jonatan Kruszewski
Senior Frontend Engineer
React architecture at application scale, and the types, tests, docs and pipelines that keep it usable a year later. Rxova is that work, done in public.
jonyk@rxova.devWhy it exists
Open source solutions for common problems
The bug
The caret jumps to the end of a currency field mid-typing.
Now a packagereact-inputs
The bug
A pasted code lands in one OTP slot instead of all six.
Now a packagereact-inputs
The bug
A branching, multi-step flow decays into booleans and effects.
Now a packagejourney
The bug
An error sent through JSON arrives as {}: its class, code and cause are gone.
Now a packagets-extended-errors
Each was solved before, privately, inside a product repo. Rxova is where that work stops being private.
See all projectsWhat the projects share
Four rules you can check against the code.
Focused APIs, DX first
One problem each, an API that feels native, and nothing to set up before the first useful line. Extras such as plugins are opt-in.
TypeScript-first, framework at the edge
journey-corethenjourney-react
The core ships apart from its React bindings, so it runs in a worker, a test, or no React at all.
Accessible and tested by default
Part of the component, not an issue filed after launch. Unit tests at 90%+ coverage, and end-to-end suites that cover the edge cases, not only the happy path.
Take one, keep your stack
pnpm add @rxova/journey-coreNo meta-package, no shared runtime. Dropping one later is a single uninstall.
Maintenance
One person's work, said plainly.
Don't trust a badge. Updates logs every release and decision, and every commit is public.
Read the Updates logYou can count on
- Issues get read
- Security reports come first
- No API break without a major and a migration note
- Extensive documentation
- High test coverage
Contributing
The most useful help is small.
A minimal repro
Worth more than a patch. Making a bug happen on demand is most of the fix.
A focused pull request
One behaviour, with the test that fails without it. Big refactors start as an issue.
A docs fix
If something cost you an hour, saying so already counts.
Issues and pull requests go to each project's repo:
- journeyDeclarative journey graphs for non-linear UI flows.
- react-inputsThe tricky React inputs, done right.
- use-everywhereState and messages that exist in every tab, window, and worker.
- ts-extended-errorsTyped, serializable errors that survive a JSON round trip.
Security or private: jonyk@rxova.dev