conflicting error to the user who is using this package

[dev-2-atsit]

he i just install this package but in you package

this react version is getting problem to the user who is using this package please update it to lates or upper version

[ssbeefeater]

Hi what's exactly the problem you are facing and what's you current react version

[dev-2-atsit]

Actully in package json of package itself using this version of react please up to date to new version >16.8.0

[ZuBB]

I have the same issue, although I admit the bug has been created poorly.

Probably, the author meant that in recently created projects run of npm i fails with the next error

vv@my-precious ~/work/freelance/living-words $ npm install react-typed --save                                                             
npm error code ERESOLVE                                                                                                                   
npm error ERESOLVE unable to resolve dependency tree                                                                                      
npm error                                                                                                                                 
npm error While resolving: living-words@0.1.0                                                                                             
npm error Found: react@19.0.0-rc-02c0e824-20241028                                                                                        
npm error node_modules/react                                                                                                              
npm error   react@"19.0.0-rc-02c0e824-20241028" from the root project                                                                     
npm error                                                            
npm error Could not resolve dependency:                                                                                                   
npm error peer react@">16.8.0" from react-typed@2.0.12               
npm error node_modules/react-typed                                   
npm error   react-typed@"*" from the root project                    
npm error                                                                                                                                 
npm error Fix the upstream dependency conflict, or retry                                                                                  
npm error this command with --force or --legacy-peer-deps                                                                                 
npm error to accept an incorrect (and potentially broken) dependency resolution.                                                          
npm error                                                                                                                                 
npm error                                                                                                                                 
npm error For a full report see:                                     
npm error /Users/vv/.npm/_logs/2024-11-14T08_49_27_741Z-eresolve-report.txt                                                               
npm error A complete log of this run can be found in: /Users/vv/.npm/_logs/2024-11-14T08_49_27_741Z-debug-0.log                           
vv@my-precious ~/work/freelance/living-words $

in dev mode this can be overcome with next command

vv@my-precious ~/work/freelance/living-words $ npm install react-typed --save --legacy-peer-deps                                          
                                                                                                                                          
added 2 packages, and audited 393 packages in 2s                     

142 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
vv@my-precious ~/work/freelance/living-words $ 

In CI mode, the approach from above might not be feasible, so local .npmrc with the corresponding option may be the desired way to go.

my env is next:

vv@my-precious ~/work/freelance/living-words $ node -v
v20.12.2
vv@my-precious ~/work/freelance/living-words $ npm -v
10.9.0
vv@my-precious ~/work/freelance/living-words $ 

[ZuBB]

I looked into this (my case) a bit deeper. There is nothing wrong with react-typed. It requires react@16.8 or higher. The bad boy here is Next.js, which is built on top of React v19. However, since React v19 has yet to be released, Next.js depends on the RC versions of React, which are not visible by default.

Our best action right now is to add legacy-peer-deps=true to the local .npmrc and pray that other libs that depend on React will work with its 19th version.

---

I do not know the case of the topic starter, but I think this issue can be closed.