3 ms·
I'm a huge fan of React Aria and have built a component lib on top of their hooks and React Aria Components(RAC). I find some downsides though around how insul
by Rapzid 3y ago
I'm a huge fan of React Aria and have built a component lib on top of their hooks and React Aria Components(RAC).
I find some downsides though around how insular the development is. Hardly any outside requests get more than "we have no plans to implement this in the near future -closed". They have a very strict interpretation of the ARIA specs, to the point escape hatches aren't afforded to those wanting to create components that match industry expectations. All the position code is custom instead of taking advantage of something like Floating UI.
It's very much a project by Adobe for Adobe. That's a fact you just have to accept, and why there is still no tree grid list, tag fields, and etc.
To end this with some praise though.. The lead dev is pretty brilliant. There are a lot of cool concepts implemented with slots and contexts which make it "easy" to create components that compose and customize based on their ancestor context. It(RAC) works perfectly well with Tailwind which I have love/hate relationship with.