Is this project abandoned?

[nouman91]

Hi,

Thank you maintainers/creators for this lib. It really helped my team in getting started with keycloak in react application. However, I see a few open issues and no reply from you guys. Moreover, there are new releases of keycloak which seems to be incompatible with this library. Any plans on upgrading this library.

Looking forward to your response

[tobiasfrei]

If you look at the issue tracker, I would say yes. For keycloak support >=17 a fork is available, the adjustments for this were trivial and would be done quickly. #180

[t-h-e]

If you are in need for an example on how to use keycloak with react. Have a look at this repo: https://github.com/dasniko/keycloak-reactjs-demo

[Paul6552]

I am a bit confused. Should we now get rid of this package? Switch to NextAuthjs or implement the whole thing without a package?

In my case I was able to switch to react 18 and keycloak/web without any problems.

I'm currently using openid-Connect as a connector. NextAuthJS would do the same thing, so why would anyone switch?

[MetaMmodern]

I am a bit confused. Should we now get rid of this package? Switch to NextAuthjs or implement the whole thing without a package?

In my case I was able to switch to react 18 and keycloak/web without any problems.

I'm currently using openid-Connect as a connector. NextAuthJS would do the same thing, so why would anyone switch?

why do you mention nextAuthjs? It doesn't work with pure react apps(alhough they started to work towards creating a more unbound library called Auth.js, but it's still WIP)