Upgrade next@15: unmet peer `@types/react@npm:types-react@19.0.0-rc.1` found `19.0.0-rc.1`
Unanswered
Havana posted this in #help-forum
HavanaOP
I'm trying to upgrade my app to next@15 and react@19 in a turborepo with pnpm.
Im getting a few weird peer deps warnings for a few packages that seem to already specifiy react@19-rc as a peer dep.
This is my app package.json:
And I have this in my monorepo root's package json:
And this is one of the peer dep warnigs I get:
And if we check
https://github.com/radix-ui/primitives/blob/main/packages/react/focus-scope/package.json#L35-L48
Any clue on what might be wrong here? I would like to avoid too many warnings on pnpm install before completing the migration (at least for the packages that are already updated)
Im getting a few weird peer deps warnings for a few packages that seem to already specifiy react@19-rc as a peer dep.
This is my app package.json:
"dependencies": {
"react": "19.0.0-rc-02c0e824-20241028",
"react-dom": "19.0.0-rc-02c0e824-20241028"
},
"devDependencies": {
"@types/react": "npm:types-react@19.0.0-rc.1",
"@types/react-dom": "npm:types-react-dom@19.0.0-rc.1"
}And I have this in my monorepo root's package json:
"packageManager": "pnpm@9.5.0",
"pnpm": {
"overrides": {
"@types/react": "npm:types-react@19.0.0-rc.1",
"@types/react-dom": "npm:types-react-dom@19.0.0-rc.1"
}
}And this is one of the peer dep warnigs I get:
@radix-ui/react-focus-scope 1.1.0
│ │ ├── ✕ unmet peer @types/react@npm:types-react@19.0.0-rc.1: found 19.0.0-rc.1And if we check
@radix-ui/react-focus-scope package.json: "peerDependencies": {
"@types/react": "*",
"@types/react-dom": "*",
"react": "^16.8 || ^17.0 || ^18.0 || ^19.0 || ^19.0.0-rc",
"react-dom": "^16.8 || ^17.0 || ^18.0 || ^19.0 || ^19.0.0-rc"
},
"peerDependenciesMeta": {
"@types/react": {
"optional": true
},
"@types/react-dom": {
"optional": true
}
},https://github.com/radix-ui/primitives/blob/main/packages/react/focus-scope/package.json#L35-L48
Any clue on what might be wrong here? I would like to avoid too many warnings on pnpm install before completing the migration (at least for the packages that are already updated)