stateless.software

What It Is

stateless-dataos is a React-oriented state library built around the idea of “Zero State”: instead of maintaining a second copy of state inside JavaScript, it treats the DOM itself as the source of truth. In the examples on the page, developers define selectors and read methods via a manifest, then call useDomState to retrieve state. This makes it closer to an htmx-style hypermedia development model, well suited to HATEOAS architectures where the backend returns HTML fragments and the frontend handles componentized rendering.

Core Capabilities and Ecosystem

Its main strength is reducing state synchronization problems. Traditional React state libraries usually require maintaining a JS state layer and keeping it in sync with the DOM representation, while stateless-dataos explicitly avoids that duplication. The page highlights that it is under 1KB gzip, built on domx, written in Pure TypeScript, and provides full type safety. It is compatible with React 16.8+, 17.x, and 18.x, and is also claimed to work with Next.js, SSR, htmx, and vanilla HTML scenarios. At the API level, the main content currently only shows useDomState(manifest), which can read DOM information such as data attributes and form values.

Pricing and Open Source

The page provides npm install stateless-dataos and a GitHub link, so it can generally be understood as an open-source npm library. No commercial pricing or paid edition is shown. However, the main content does not clearly specify the license, commercial usage terms, maintenance team, or versioning strategy, so companies should review the GitHub repository further before adopting it.

Pros and Cons

Its advantages are a clear concept, extremely small package size, TypeScript friendliness, and a strong fit for hypermedia/HATEOAS-style projects. It can reduce the duplicated state and synchronization complexity commonly found in approaches such as Redux, Zustand, and signals. The downsides are also obvious: using the DOM as the state source is a relatively specialized paradigm, and teams need to rethink how they model state. For complex client-side state, offline caching, large amounts of local business logic, or cross-page state sharing, the page does not provide sufficient detail.

Who It’s For and Access from China

It is suitable for developers familiar with React who want to build backend-driven UIs or HTML fragment workflows, as well as projects that want lightweight interactivity with fewer dependencies. The page does not provide information about access from China. npm and GitHub availability may depend on the local network environment. Alternatives include Redux, Zustand, Jotai, Valtio, React useState/useReducer, and using htmx directly.