react-strict-dom: newest release October 2025, branch moved August 2026, every link still on the old org
React Strict DOM (RSD) standardizes the development of styled React components for web and native.
At a glance
- What is it?
- A monorepo from the React organisation that standardises styled components across web and native, with styling compiled through a PostCSS plugin. The repository moved owners and kept its old links, its published package is a year behind its source, and one lint plugin is pinned to a dated canary build.
- Who is it for?
- Read it as what its own title says, a development monorepo, and not as the product. The published package is a year behind the branch, every version on the registry is a zero-point-zero release with no stability guarantee attached, and the documentation it links to sits on a different address from the one it declares.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- react/react-strict-dom3,578 ★ · +11
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| react/react-strict-dom | 3.6k | 3.6k |
11 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The published package is a year behind the branch
Compare the two dates. The default branch received a push on 2026-08-31. The three newest releases are 0.0.52, 0.0.53 and 0.0.54, published on 29 September, 1 October and 2 October of 2025. So the newest artefact anyone can install is roughly eleven months older than the newest source, and the three most recent releases came out within four days of each other in a single burst. The version scheme compounds it: every published version is a zero point zero release, which is the conventional marker for something that has not stabilised. So there is no version you can point at and say this is the tested state, and the gap between the tag and the branch is where unreleased work lives. Anyone reading the source to understand the library is reading something no user has.
Every internal link still names the previous organisation
The repository sits under one organisation and every link in its readme names another. The structure section links each example application and package through the old path, the test badge points there, the contributing guide points to a documentation site hosted on the old namespace, and the code of conduct is the previous employer's open source policy. The declared homepage is the new namespace while the documentation link inside the readme is the old one. Forks redirect at the forge, so the links work and nothing appears broken, which is the problem: an organisation rename leaves every internal reference silently pointing somewhere that is no longer where the project is governed from. It also means the governance and the code are now nominally owned by two different organisations, with the code of conduct still naming the other one.
One lint plugin is pinned to a dated canary build
The development dependencies are all ordinary caret ranges, with one exception that stands out:
"eslint-plugin-react-hooks": "6.1.0-canary-12bc60f5-20250613"An exact version of a pre-release build, dated mid-2025, pinned to what looks like a commit identifier, sitting in a list where everything else is allowed to float. Two things follow. The plugin is the one dependency in the list that cannot move on its own, so it will be the first thing that breaks when the rest of the toolchain moves, and it is a canary, so the artefact it points at may never be republished. It is also the plugin that enforces the rules about hooks, which is not a place to accept a lint blind spot. This is the kind of pin that gets added quickly to unblock a release and then never revisited.
The lint and format tooling is built around an engine's parser
The type system here is Flow rather than TypeScript, which the dependency list confirms through a type checker binary, a preset, a comment transform that strips types during compilation, and a lint plugin for its syntax. The surprising part is the parser. Alongside those there are three separate packages named for a JavaScript engine's parser, wired into the compiler, into the linter and into the formatter respectively:
"babel-plugin-syntax-hermes-parser": "^0.36.1"
"hermes-eslint": "^0.36.1"So linting and formatting do not use the standard parser, they use an engine's. That buys consistency between what the engine accepts and what the tools accept, which is a real benefit for a project targeting a specific runtime. It also means the whole style and lint pipeline is coupled to one engine's grammar, and upgrading it is a coordinated change across three tools rather than one. Separately, the linter is on its eighth major with the older configuration format, which is the last release line before that format was superseded.
Installing the monorepo applies patches, clears a cache and builds
The postinstall step is three commands:
"postinstall": "patch-package && npm run jest -- --clearCache && npm run build"So a plain install applies patches to dependencies, discards the test runner's cache, and runs a full build of every workspace. That is a heavy postinstall for a monorepo that people clone to read, and it runs before anyone has looked at anything. It also explains a detail: the patching tool expects a patch directory at the root of the project, and the root listing does not contain one. So on a fresh clone the first of those three commands has nothing to apply, which is harmless, but it is the kind of thing that gets noticed when an install is slow and unexplained. The separate prepare step installs the commit hooks from a directory inside the tools folder.
A mistyped workspace script is skipped instead of reported
The build and test scripts at the root are written as loops over the workspaces with a flag that means carry on if the script is missing:
"build": "npm run build --workspaces --if-present",
"jest:report": "npm run jest:report --workspaces --if-present --",That flag is what lets one root script drive five packages that do not all have the same scripts. It has a second effect that is easy to miss: if a package's script is renamed or misspelled, the flag turns what should be a hard failure into a silent skip. The root test command chains the type check, the lint report and the test report, so it will pass with one workspace not running at all. This is a normal trade in a monorepo, and it is worth knowing when a green build tells you less than it appears to.
The one architectural fact in the readme is that styling is compiled
The readme is short, and almost all of it is a directory listing. The structure section names five example applications, an interface example, two framework applications for server-rendered and Vite-based builds, one for Expo, and a platform test suite. Then five packages: benchmarks, the library, its documentation site, its scripts, and one that explains the whole design by being a build plugin. That last one is the architecture. Styling is not resolved at runtime; a PostCSS plugin compiles the style props so the same source produces web and native output. The rest of the stated goal follows from that: the same component written once, compiled per platform. Everything else in the file is navigation, so a reader wanting the design has to infer it from a package name.
Editorial conclusion
Read it as what its own title says, a development monorepo, and not as the product. The published package is a year behind the branch, every version on the registry is a zero-point-zero release with no stability guarantee attached, and the documentation it links to sits on a different address from the one it declares. Two things make it worth reading anyway. The one architectural fact the readme gives is that styling is handled by a build plugin rather than at runtime, which is the right shape for a library that has to produce both web and native output from one source. And the fact that the owning organisation changed without the links being rewritten is a useful warning for anyone maintaining a monorepo under a company umbrella: the redirects keep working, which is exactly why nobody fixes them. Verify the version you install against the branch you read.
Frequently asked questions
what is react strict dom
It is a library that standardises the development of styled components for web and native from one source, with style handling done by a build plugin rather than at runtime. The stated goal is to improve the speed and efficiency of development without compromising performance, reliability or quality. The repository is the development monorepo for it, containing the library, a PostCSS plugin, benchmarks, a website and five example applications.
What is the difference between React Strict Mode and React Strict DOM?
The repository documents only the second. React Strict DOM is described as a library for styled components across web and native, with a PostCSS plugin, a benchmark package, a website and example applications including ones for two web frameworks and one for Expo. Nothing in this repository describes React Strict Mode or compares the two.
Which version of react-strict-dom should I install?
Every published version is a 0.0.x release, the newest being 0.0.54 from 2025-10-02, while the default branch was pushed on 2026-08-31. So the published package is about eleven months behind the source, and no release carries a stability guarantee. Reading the branch and installing the tag will not give you the same code.
How is react-strict-dom built and tested?
The root scripts loop over the workspaces with a flag that skips packages missing a given script, and the root test command chains a Flow type check, a lint report and a test report. Installing the monorepo applies dependency patches, clears the test cache and runs a full build, and a prepare step installs commit hooks from a directory inside the tools folder.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/react-react-strict-dom)Star history chart for your README
[](https://hysenlabs.com/projects/react-react-strict-dom)Was this useful?