Rxova
← All repos

Journey

Updates mentioning Journey. See the repository ↗ for commits and releases.

  1. A new landing page for Journey

    Journeydocs

    The Docusaurus migration transcribed the old homepage rather than redesigning it, so it still opened as a release announcement — “We did it!”, a confetti modal, a link to reopen the 1.0.0rc celebration — and four sections carried the old teal-and-navy palette as some fifty hardcoded colour literals, on a site whose accent has been violet since it adopted @rxova/brand. The carousel’s cards filled with the token the brand maps to the page background, so only a hairline of them showed.

    Those four components are gone, along with every hardcoded colour and the confetti dependency, replaced by sections built the way the react-inputs landing is built: brand tokens only, prefers-reduced-motion on every animation, and server-rendered content so the page reads with JS off. The demo runs a real @rxova/journey-core machine from a plain script through a branching checkout — no React, no bindings — which demonstrates the framework-agnostic claim rather than asserting it.

    The proof band measures itself: size-limit runs against each package’s built output at build time and the coverage floor is parsed out of the vitest config, so no figure is restated from prose. It immediately caught one — the bridge measures 3.13 kB, not the 3.2 kB the README claims.

    Jonatan Kruszewski

  2. The docs ingest contract

    WebsiteJourneyuse-everywherereact-inputsinfra

    rxova.org used to check out three repos and build their docs itself, which meant one project’s broken build took the whole site down with it.

    Each repo now builds its own docs and ships them as a release asset; the site ingests the artifact. A project either publishes something valid or the site keeps serving the last good copy.

    Jonatan Kruszewski

  3. Clearing the audit backlog

    Journeyreact-inputsuse-everywherefixinfra

    pnpm audit is only useful if it is ever green. svgo was pinned to a vulnerable 3.3.3 by an override, so it got unpinned; brace-expansion, js-yaml, webpack-dev-server and dompurify were resolved behind it.

    Dropping Docusaurus left sixteen overrides pointing at packages no longer in the tree, and those went too — a stale override is a silent way to hold a dependency back.

    Jonatan Kruszewski

  4. One Turborepo standard across every repo

    Journeyuse-everywherereact-inputsBrandinfra

    Four repos had drifted into four ways of running the same six checks. They now share one Turborepo pipeline and one CI shape, so a fix to the build order is made once.

    Node 24, TypeScript 6 and pnpm 11 across all of them, which also got pnpm audit working again.

    Jonatan Kruszewski

  5. Docusaurus out, Astro Starlight in

    use-everywherereact-inputsJourneydocsfeature

    All three docs sites moved to Astro Starlight. The landing already was Astro, so this leaves one framework across the whole origin — and dropped a webpack build that had been the flakiest job in every pipeline.

    react-inputs took the chance to restructure: one component library with a flat sidebar and shared guides, instead of three manuals bolted together.

    Jonatan Kruszewski

  6. Every docs site points at the aggregator

    Journeyreact-inputsuse-everywhereinfra

    Each project used to deploy its own GitHub Pages site at its own URL. All three stopped, and now take their url and baseUrl from the environment instead of hardcoding one.

    The same build therefore works standalone at / and mounted at /packages/<name>/, which is what let rxova.org host them without forking anything.

    Jonatan Kruszewski