@example/components-react declares react@18 as a peer dependency, but devDeps already use react@^19.
Consumers on React 19 currently get peer-dep warnings on install.
Could the peer range be widened to "18 || 19" so both are supported?
Same question for @example/web-components-react, which is still on ^17.0.2.
@example/components-reactdeclaresreact@18as a peer dependency, but devDeps already usereact@^19.Consumers on React 19 currently get peer-dep warnings on install.
Could the peer range be widened to
"18 || 19"so both are supported?Same question for
@example/web-components-react, which is still on^17.0.2.