
The React ecosystem keeps growing stronger, with new tools and libraries enhancing how we build apps. Here's my curated list of must-have React lib...
For further actions, you may consider blocking this person and/or reporting abuse
Cool ones, thanks for the share! Here are some more great ones:
For auth, I wonder if it is more common to implement auth UI server side using python or go or whatever is on the backend rather than client side?
you can use next-auth in both sides server and client.
So are you also suggesting people serving node backend with express, nestjs, or other servers are using auth.js for that?
But that still makes me wonder about python, rails, and go, which will be just as common for react backends. In those cases, are people not using any react library and delegating to flask/django/rails/etc?
no, i mean you can use auth for a next app and you can implement in server actions or functions as well as client components, a separate backend must implement other strategy or adapt in some way to use the tokens or session from next-auth
Cool list.
If you like building with React checkout StyleX
github.com/facebook/stylex
Thank you for calling out wouter!!
Nice breakdown! But do people really prefer Wouter?
also react-router is very popular. it depends. IMO. i prefer wouter, i used to use it and i like it a lot.
What do you think about zustand vs using plain reducer + context?
I think Zustand is easier to use and understand