react-spectrum
react-spectrum copied to clipboard
peerDependencies still limited to ^19.0.0-rc.1 in react-aria and react-aria-components (causes npm peer warnings/errors)
Provide a general summary of the issue here
Installing react-aria and/or react-aria-components with React 19 stable triggers peerDependency warnings/errors because the packages list React 19 only as a prerelease (^19.0.0-rc.1) rather than including ^19.0.0. This is a metadata issue (semver range), not a runtime incompatibility.
Packages observed:
Both declare peers:
- react, react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
π€ Expected Behavior?
Installing react-aria/react-aria-components alongside React 19 stable (e.g., 19.2.0) should not produce peerDependency warnings or install errors. Peer ranges should include React 19 stable, e.g.: react, react-dom: ... ^18.0.0 || ^19.0.0
π― Current Behavior
npm install emits peer warnings or can error with ERESOLVE because 19.2.0 does not satisfy the peer range "^19.0.0-rc.1".
react-aria requires react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" but react 19.2.0 is found react-aria requires react-dom@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" but react-dom 19.2.0 is found
π Possible Solution
Please widen peerDependencies for all affected packages to include React 19 stable:
Suggested range: react, react-dom: ... ^19.0.0 Runtime appears fine on React 19 stable; the issue is purely metadata.
π¦ Context
Context Weβre adopting React 19 stable across our component library. Our main application uses this library but is RC-only. This creates noise in CI and friction for downstream consumers while the code itself runs fine with React 19.
π₯οΈ Steps to Reproduce
Create a new project with pnpm, React 19.2.0, React Aria Components 1.13.0, and react aria 3.44 Run pnpm install
Version
react-aria 3.44.0 react-aria-components 1.13.0
What browsers are you seeing the problem on?
Microsoft Edge, Other
If other, please specify.
No response
What operating system are you using?
Windows 11 Enterprise
π§’ Your Company/Team
No response
π· Tracking Issue
No response