React 18 StrictMode about use-http HOT 22 OPEN

Seconding this, I'm getting unable to resolve dependency tree when trying to install on a new React project...

from use-http.

It will give you an error.

More a warning I would say, this library has not been certified compatible with React v18 yet.
I have been using it with React v18 without too much problems other than this issue here with <StrictMode />

If you happen to know a way to make it fully compatible with React v18, feel free to contribute, this is Open Source ;)

from use-http.

Oh okay, I have not used npm in years now, did not know it would prevent to install it 🤷
yarn just warns about the version potentially not supported. the --force flag of npm should work until this issue is resolved

from use-http.

If someone creates a PR for this I'll gladly accept it.

from use-http.

@krishnasaga it's MIT licensed, you already have permission.

from use-http.

It installs fine for me, try with --legacy-peer-deps flag.

from use-http.

It installs fine for me, try with --legacy-peer-deps flag.

Thanks , indeed it installs with this flag , however, in runtime I realized that use-http doesn't work with React.StrictMode and React 18...
found a related issue :
#368

from use-http.

Did any one found the root cause of what causing this ?

from use-http.

zvi1977 I added my findings of root cause here #368 (comment).

#368

from use-http.

How is it even possible that this library is not supporting v18? :O

from use-http.

@enriquemorenotent what do you men by not supporting ?

from use-http.

@krishnasaga Have you tried doing npm i use-http on a React v18 app? It will give you an error.

You can "force it", of course. But it doesn't inspire a lot of confidence.

from use-http.

@enriquemorenotent There reason you receive this error is because of this

By resolving this issue and successfully passing all the tests. use-http can start supporting react 18. then we can update the pear dependencies so you will not get that error when you install it.

from use-http.

@krishnasaga I am not sure I understand what you are asking me...

from use-http.

@flo-sch I would call it a warning, if it actually installed the package. But since it doesn't, I call it an error.

Sadly no, I have no idea how to make it work.

from use-http.

@alex-cory there is a duplicate of this thread which I have mentioned. If it making sense to close one of those could you do it please ?

from use-http.

@alex-cory Can I have your permission to copy the code of use-http to use directly in my project without importing, so I can have have that fix in my project without needing to depend on the release and also allows me to battle test it against multiple scenarios.

from use-http.

Is there a timeline on react 18 support? our company pipeline doesnt allow force or using legacy deps when doing npm install

from use-http.

Lol, that's something I never heard of. For me 9 out of 10 projects have to use --legacy-peer-deps. Just because a package hasn't been updated since the release of npm v7 it doesn't mean it's a security risk.

from use-http.

from use-http.

from use-http.

from use-http.