The published packages (@cratis/components.primereact, .primereact10, .mui, .conformance) declare engines.node >=23.0.0, and the repository root does too. Node.js 23 is end of life, and >=23 excludes Node.js 22, a maintenance LTS release until 2027-04-30. Package managers that enforce engines (pnpm and npm with engine-strict) refuse installs on Node.js 22, although nothing in the packages is known to need 23. @cratis/components itself declares no engines, and @cratis/components.migrator declares >=20.0.0.
Decide the supported range, for example >=22 (every maintained LTS release) or >=24 (active LTS only), and prove it with a packed-consumer check on the lowest supported version. Narrowing the range is a breaking change for anyone installing on a release it excludes. Widening it is compatible, but it should come with CI evidence on that version.
The published packages (
@cratis/components.primereact,.primereact10,.mui,.conformance) declareengines.node >=23.0.0, and the repository root does too. Node.js 23 is end of life, and>=23excludes Node.js 22, a maintenance LTS release until 2027-04-30. Package managers that enforce engines (pnpm and npm withengine-strict) refuse installs on Node.js 22, although nothing in the packages is known to need 23.@cratis/componentsitself declares no engines, and@cratis/components.migratordeclares>=20.0.0.Decide the supported range, for example
>=22(every maintained LTS release) or>=24(active LTS only), and prove it with a packed-consumer check on the lowest supported version. Narrowing the range is a breaking change for anyone installing on a release it excludes. Widening it is compatible, but it should come with CI evidence on that version.