Published compatibility
Boreal separates consumer peer compatibility from the toolchain used to build
the repository. Compatibility is verified from packed npm artifacts in isolated
temporary consumer projects; source imports and the workspace's root
node_modules are not used.
| Package | React | ReactDOM | Next | Node |
|---|---|---|---|---|
@boreal-ui/core |
>=18.2.0 |
>=18.2.0 |
— | No package engine; verified on Node 20 and 22 |
@boreal-ui/next |
>=18.2.0 |
>=18.2.0 |
>=13.0.0 |
No package engine; verified on Node 20 and 22 where the selected Next version permits it |
@boreal-ui/types |
>=18.2.0 |
>=18.2.0 |
— | No package engine |
@boreal-ui/docs |
— | — | — | No package engine |
@boreal-ui/cli |
— | — | — | >=18 |
The Boreal workspace itself requires Node ^20.19.0 || >=22.12.0. This is a
build/development constraint, not a peer requirement imposed by the runtime
packages.
Verified matrix
CI exercises these representative boundaries:
- React 18.2 and the current React 19 line with
@boreal-ui/core. - Next 13.5.11 with React 18.2, Next 15.5 with React 19, and the current Next 16 line.
- Node 20.19 and Node 22.12 for runtime packages.
- Node 18.20 and Node 22.12 for the CLI.
The framework lanes respect Next's own published constraints. Each Core fixture
checks declarations, ESM bundling, styles, representative rendering, context,
forms, and interaction. Each Next fixture type-checks and runs a production App
Router build containing client components and @boreal-ui/next/server imports.
TypeScript does not currently have a separately published support range. The generated declarations are checked with the repository's current TypeScript version in every React and Next fixture.