Create components whose nested prop changes map to a global side effect
by gaearonJavaScript
Last 12 weeks · 0 commits
2 of 6 standards met
Overview Adds React 19 peer dependency support. Also changed _a lot_ of outdated dependencies (some of the open PRs may now be redundant). ~No runtime code needed to be changed thankfully~ I changed to and all test pass. This is a good sign. Renovate bot and a yarn GH workflow for this repo would be great!
Repository: gaearon/react-side-effect. Description: Create components whose nested prop changes map to a global side effect Stars: 1220, Forks: 78. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Latest release: v2.1.2 (3y ago). Open PRs: 6, open issues: 9. Last activity: 3y ago. Community health: 42%. Top contributors: lourd, gaearon, realityking, lo1tuma, dependabot[bot], davidfurlong, browniebroke, dimitrinicolas, gannoncurran, glenjamin and others.
Updating my React.js code I realize that this dependency (on which react-helmet depends) is the only one that is not updated to React 19: npm warn ERESOLVE overriding peer dependency npm warn While resolving: react-side-effect@2.1.2 npm warn Found: react@19.1.0 npm warn node_modules/react npm warn react@"^19.1.0" from the root project npm warn 24 more (@emotion/react, ...) npm warn npm warn Could not resolve dependency: npm warn peer react@"^16.3.0 ^18.0.0" from react-side-effect@2.1.2 npm warn node_modules/react-helmet/node_modules/react-side-effect npm warn react-side-effect@"^2.1.0" from react-helmet@6.1.0 npm warn node_modules/react-helmet npm warn npm warn Conflicting peer dependency: react@18.3.1 npm warn node_modules/react npm warn peer react@"^16.3.0 ^18.0.0" from react-side-effect@2.1.2 npm warn node_modules/react-helmet/node_modules/react-side-effect npm warn react-side-effect@"^2.1.0" from react-helmet@6.1.0 npm warn node_modules/react-helmet Can it be fixed? Kind regards.
Same as #69 but for React 18 :) Like @karlhorky, I came here from a react-helmet warning: @lourd do you think we could write this peer dependency without upper bound, something like: ?