peerDependencies still limited to ^19.0.0-rc.1 in react-aria and react-aria-components (causes npm peer warnings/errors)

[JonasSchiessl]

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:

• react-aria@3.44.0
• react-aria-components@1.13.0

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

[snowystinger]

I am not sure that's true, npm's semver includes the stables when I try it on their site
https://semver.npmjs.com/
"react"
"^19.0.0-rc.1"
After listing the versions, I can see them in the list at the bottom.

Is this an issue in pnpm perhaps?

[JonasSchiessl]

the problem only appears when importing our library and using it in another project. In the library itself it shows correctly however once you import it you get this warning.

[devongovett]

You should verify that you don't have multiple versions installed in your lockfile.

Otherwise we will need a reproduction of the issue.

[ashleyyy94]

Getting the same issue when trying to upgrade React in my project. This is the error thrown by npm due to the dependency array in our own component library (csl-palette):

npm error Found: react@19.2.1
npm error node_modules/react
npm error   react@"^19.2.1" from the root project
npm error   peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1" from @react-aria/autocomplete@3.0.0-rc.3
npm error   node_modules/@react-aria/autocomplete
npm error     @react-aria/autocomplete@"3.0.0-rc.3" from react-aria-components@1.13.0
npm error     node_modules/react-aria-components
npm error       react-aria-components@"^1.9.0" from csl-palette@0.32.30
npm error       node_modules/csl-palette
npm error         csl-palette@"^0.32.30" from the root project
npm error   121 more (@react-aria/breadcrumbs, @react-aria/button, ...)

There are no multiple versions installed as well and installing the latest release of react-aria also has the same issue.

[devongovett]

npm install react react-dom react-aria-components succeeds for me with no errors. Please provide a reproduction.

[ashleyyy94]

I think it's quite hard to provide a reproduction as first we'll have to create a component library that uses react-aria-components, publish that, and then let you install that library in order to see it....

I think the simplest solution is in the original post no?

💁 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.

[snowystinger]

No need to publish anything, the reproduction can include a tool like verdaccio https://verdaccio.org/ for local publishing if needed. Or you may be able to locally link instead.

[ashleyyy94]

I am not sure that's true, npm's semver includes the stables when I try it on their site semver.npmjs.com "react" "^19.0.0-rc.1" After listing the versions, I can see them in the list at the bottom.

Is this an issue in pnpm perhaps?

I raised a PR for this instead of setting up a local reproduction as I'm pretty busy with other stuff at work, my apologies. Appreciate the time taken to look into this.

At the same time, I think the semver has been updated for React:

[snowystinger]

I'm very sorry, but I'm not sure what you're showing in the screen shot. That doesn't match the proposal nor current usage. So what is it you're trying to show there?

[ashleyyy94]

Pardon me, the version range input field should have been ^19.0.0-rc.1, which does match all versions of react. I'll investigate more on my own packages on the likely cause of the error thrown by npm then. Thanks! :)