Update package.json to modify react-is dependency

[mattcosta7]

This pull request updates the dependencies in the packages/react/package.json file, primarily focusing on upgrading react-related packages and ensuring compatibility with new versions. The most significant changes include the addition and upgrade of react-is and its associated type definitions, as well as adjustments to peer dependencies.

Primer fails to install in a react 19 project because the dependency on react-is conflicts, by making it a peer we avoid that conflcit

Changelog

New

Changed

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

🦋 Changeset detected

Latest commit: 93527df

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/react	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!

[mattcosta7]

optional peer

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	92.26 KB (0%)
packages/react/dist/browser.umd.js	92.35 KB (0%)

[Copilot]

Pull Request Overview

This PR resolves a React 19 compatibility issue by converting react-is from a direct dependency to a peer dependency, preventing installation conflicts when Primer is used in React 19 projects. The change also updates related TypeScript type definitions and ensures proper version compatibility.

Key changes:

• Moved react-is and @types/react-is from dependencies to peer dependencies with version ranges supporting both React 18.x and 19.x
• Updated TypeScript type definitions for React-related packages to newer patch versions
• Added optional peer dependency metadata for @types/react-is

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
packages/react/package.json	Restructured dependencies to move react-is to peer dependencies and updated type definitions
.changeset/tall-pets-obey.md	Added changeset entry documenting the peer dependency corrections

[primer-integration]

👋 Hi from github/github! Your integration PR is ready: https://github.com/github/github/pull/392407

[joshblack]

For context on removing from the queue, just was waiting for the integration PR to pass 👀

The only thing I'm worried about is adding a new peerDependency here in a minor release since they are not auto-installed so we will need to update install instructions to include this now.

Could we instead update the range on the dependency? e.g. "react-is": "18.x || 19.x" or would that not work as expected?

[primer-integration]

🟢 golden-jobs completed with status success.

[mattcosta7]

For context on removing from the queue, just was waiting for the integration PR to pass 👀

The only thing I'm worried about is adding a new peerDependency here in a minor release since they are not auto-installed so we will need to update install instructions to include this now.

Could we instead update the range on the dependency? e.g. "react-is": "18.x || 19.x" or would that not work as expected?

NPM started installing peerDependencies by default in version 7 https://github.blog/news-insights/product-news/npm-7-is-now-generally-available/#peer-dependencies

Automatically installing peer dependencies is an exciting new feature introduced in npm 7

I don't think we should be installing a version of it for consumers and 2 versions installed could cause some conflcits I think? (although they're generally backwards compat). With that said, a broader dependency might be ok - but is probably not ideal?

[joshblack]

Oh nice! Didn't realize that was added (thanks for sharing)

I don't think we should be installing a version of it for consumers and 2 versions installed could cause some conflcits I think?

What scenarios would you expect to have two versions installed? Was trying to think through it:

Type	Primer	Consumer	Installed
dependencies	v18	v19	v18, v19
peerDependencies	v18	v19	Would this be an error with the new behavior in npm v7?
dependencies	v18 || v19	v19	v19
peerDependencies	v18 || v19	v19	v19

Are there any that I'm missing? 👀

[mattcosta7]

Oh nice! Didn't realize that was added (thanks for sharing)

I don't think we should be installing a version of it for consumers and 2 versions installed could cause some conflcits I think?

What scenarios would you expect to have two versions installed? Was trying to think through it:

Type Primer Consumer Installed
dependencies v18 v19 v18, v19
peerDependencies v18 v19 Would this be an error with the new behavior in npm v7?
dependencies v18 || v19 v19 v19
peerDependencies v18 || v19 v19 v19
Are there any that I'm missing? 👀

I think they generally should resolve to a single version, but I could see npm nesting one inside the pacakge instead when upgrading - I don't think it's a common case where that would happen instead of hosting, but maybe not impossible?

[joshblack]

Sounds good 👍 Definitely down to try this out. Thanks for making the PR!

[mattcosta7]

Sounds good 👍 Definitely down to try this out. Thanks for making the PR!

no problem! thank you!