[core] Add React 19 as peer dependency

[aarongarciah]

Includes v19 in React peer dependencies definitions.

How to test?

1. Clone this repo: https://github.com/aarongarciah/material-ui-react-19 (it points to v19 React deps and points Material UI deps to the CodeSandbox CI version of the library generated in this PR)
2. Install dependencies: npm i
3. Start dev server: npm start
4. Build: npm run build
5. Check that there's not TypeScript errors.

Follow the same steps with other package managers like pnpm and yarn.

---

Findings:

• Installing dependencies using npm (teted in Node v18 and v20) results in an error with an @emotion/react peer dep. To overcome the error, you need to use the --force flag (--legacy-peer-deps doesn't work).
  
• pnpm and yarn (v1) seem to work well
• No TypeScript errors reported.

[mui-bot]

Netlify deploy preview

https://deploy-preview-43216--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 2a23681

[aarongarciah]

edit: I removed the peer dependency from Joy UI and Base UI.

---

@mnajdova @DiegoAndai I need to test more components/hooks to see if users can run into TypeScript errors while using React 19. Since we still haven't merged type updates required for React 19 (we can't merge them until they're stable), there's a change some users import some component with incompatible types.

Not so many TS changes are required in the React PR. I'll review them to see if some public types (the ones we ship in .d.ts files) can break consumers' apps.

Base UI	Joy UI	Material UI

[aarongarciah]

BTW, not sure we should be updating Base UI peer deps anymore. Thoughts?

[DiegoAndai]

not sure we should be updating Base UI peer deps anymore.

I agree we shouldn't, we could skip Joy as well IMO 🤔

[aarongarciah]

Hey @Janpot, do you know if there's a way to circumvent the error described in this PR description while installing dependencies with npm apart from using npm i --force?

[Janpot]

Doesn't look like npm accepts prerelease versions as a valid version in the peer dependency range. Interestingly, looks like pnpm and yarn do accept it. You can verify the versions npm accepts here https://semver.npmjs.com/

I guess the only way (apart from forcing it) will be to wait for a stable release.

[aarongarciah]

Weird that >= 19.0.0-rc-0 lists all v19 RC releases in https://semver.npmjs.com but ^17.0.0 || ^18.0.0 || >= 19.0.0-rc-0 doesn't. I'll test by pushing another commit to generate a new version using the range syntax.

[Janpot]

I'll test by pushing another commit to generate a new version using the range syntax.

🤔 It seemed to me that the problem was that it doesn't satisfies emotion peer dependency range. I don't think we can fix that in our packages.

[aarongarciah]

Just tested with a @mui/material version using "react": "^17.0.0 || ^18.0.0 || >= 19.0.0-rc-0" and it didn't work with npm i.

I'm testing all possible range syntaxes and I don't quite understand how npm resolves ranges: ^17.0.0 || ^19.0.0-rc lists all rc releases but ^18.0.0 || ^19.0.0-rc or ^17.0.0 || ^18.0.0 || ^19.0.0-rc doesn't.

[aarongarciah]

🤔 It seemed to me that the problem was that it doesn't satisfies emotion peer dependency range. I don't think we can fix that in our packages.

My thinking is other dependencies depending on @mui/material will hit the same issue we're seeing with emotion.

[Janpot]

My thinking is other dependencies depending on @mui/material will hit the same issue we're seeing with emotion.

As soon as React releases a stable 19 version, it will satisfy the emotion peer dependency range and this error should disappear. If people want to play around with prereleases, they can just use the --force flag, no?

[aarongarciah]

@Janpot yes, I think we don't have a choice 👍

[mnajdova]

🚢 it.

Btw, we could update the installation docs once React 19 is stable with a note for the Emotion peer dependency & version compatibility problem.