Supprot React 17 in peer dependency declaration
See original GitHub issueWith the support added for React 18, we’ve ended up with the following peer dependency declarations:
https://github.com/fullcalendar/fullcalendar-react/blob/master/package.json#L47-L48
"peerDependencies": {
"react": "^16.7.0 || ^18",
"react-dom": "^16.7.0 || ^18"
},
This will trigger incorrect peer dependency warning for React 17, even though I don’t think it should. Do we need ^17
be included as the version also?
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Widen peer dependency range to include React 17 · Issue #814
@foaadnami the error is saying that there's a peer dependency conflict, because you've installed React 17 but next-auth currently requires React ...
Read more >npm Peer Dependencies - Fathom
Peer dependencies effectively declare a dependency without including the dependency in your built module. When an application includes your module, ...
Read more >Addressing the shortcomings of peer dependencies - HackMD
MUI declares React 17 as a dependency; App host declares React 18 and MUI as dependencies. When you npm install, we have a...
Read more >What does npm install --legacy-peer-deps do exactly? When ...
This error will fire whenever a module (or any of its own dependencies) lists a previous major version of React as a peerDependency...
Read more >Understanding Peer Dependencies in JavaScript
In this case, you would declare React as a peer dependency for your components, because you want the host project to have the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I released the fix in v5.11.1. Can someone please confirm?
Can confirm 5.11.1 fixes this. Thanks @arshaw !