What happens
Published @cratis/components 3.4.0 declares @cratis/arc and @cratis/arc.react peer ranges of >=20.3.1 <22. A consumer installing Arc 22.0.1 therefore receives YN0060 peer-range failures even though Components 3.4.0 is the current Components release used for the measured graph.
Evidence
An exact consumer install with Arc and Arc React 22.0.1 produced four YN0060 peer-range failures. The published Components 3.4.0 package declares the <22 peer ceiling. No matching Components issue was found through searches for Arc 22 peer support, @cratis/arc 22, and YN0060.
What it costs a consumer
A consumer cannot adopt Arc 22 as a supported dependency graph without knowingly accepting an incompatible peer declaration. The peer ceiling blocks the new Arc APIs independently of whether Components itself uses those APIs.
Suggested fix — the seam
Run Components' published-package, query-table, dialog, and provider compatibility suites against Arc 22. If compatible, widen the Arc and Arc React peer ranges and publish a stable Components release carrying that support.
What is explicitly not being asked for
This report does not ask consumers to suppress YN0060, force an unsupported dependency graph, or couple Components to Arc 22-specific APIs. It asks only for an evidence-backed peer-range decision and release.
What happens
Published
@cratis/components3.4.0 declares@cratis/arcand@cratis/arc.reactpeer ranges of>=20.3.1 <22. A consumer installing Arc 22.0.1 therefore receivesYN0060peer-range failures even though Components 3.4.0 is the current Components release used for the measured graph.Evidence
An exact consumer install with Arc and Arc React 22.0.1 produced four
YN0060peer-range failures. The published Components 3.4.0 package declares the<22peer ceiling. No matching Components issue was found through searches for Arc 22 peer support,@cratis/arc 22, andYN0060.What it costs a consumer
A consumer cannot adopt Arc 22 as a supported dependency graph without knowingly accepting an incompatible peer declaration. The peer ceiling blocks the new Arc APIs independently of whether Components itself uses those APIs.
Suggested fix — the seam
Run Components' published-package, query-table, dialog, and provider compatibility suites against Arc 22. If compatible, widen the Arc and Arc React peer ranges and publish a stable Components release carrying that support.
What is explicitly not being asked for
This report does not ask consumers to suppress
YN0060, force an unsupported dependency graph, or couple Components to Arc 22-specific APIs. It asks only for an evidence-backed peer-range decision and release.