fix(deps): enable react ^18 in peerDeps

[falsepopsky]

Summary

When you are working with react + react-dom version ">=18" and you try to install this package @carbon/react npm throw an error, like this

Could not resolve dependency:
npm ERR! peer react@"^16.8.6 || ^17.0.1" from @carbon/[email protected]

So you have 2 options

1. Install like this with -flag:

npm i @carbon/react --legacy-peer-deps

2. Update peerDependencies in package.json in react and carbon-components-react packages

To reproduce this error copy the example next folder outside from the monorepo, run npm install and you will see the error make sure you don't run --legacy-peer-deps flag.

New

• Support react >=18

Changed

• peerDependencies

Removed

• {{removed thing}}

Testing / Reviewing

[github-actions]

DCO Assistant Lite bot All contributors have signed the DCO.

[netlify]

✅ Deploy Preview for carbon-components-react ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	fe6a366
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-components-react/deploys/62d998c4733f970008150083
😎 Deploy Preview	https://deploy-preview-11826--carbon-components-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for carbon-elements ready!

Name	Link
🔨 Latest commit	fe6a366
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-elements/deploys/62d998c43e3cef0008c35051
😎 Deploy Preview	https://deploy-preview-11826--carbon-elements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[falsepopsky]

I have read the DCO document and I hereby sign the DCO.

[dakahn]

@tay1orjones adding a third set of eyes on this change

[tay1orjones]

Hi there @falsepopsky! Thanks for proposing this change. Unfortunately we haven't finished formal support for React 18 yet and so can't merge this until we land #11308

The two workarounds you listed are the recommended path for now until we can validate React 18 support within the project.