zag VS primeng

Zag.js and Ark are headless component libraries created by the teams behind Chakra UI.

ChakraUI: An emphasis on A11y, meaning it is fully compatible with the WAI-ARIA accessibility standard, has won OSS awards, and has a thriving community. As mentioned, it’s one of the better choices out there as it has a great model for building composable UI, built-in hooks, and great dark-mode support. This is the same team behind Zag.js, which handles UI as state machines. Once again, you’d need to learn the API, and swapping might be hard to do.

I agree with what another poster said about Zag (also part of the Chakra project). It seems to me that eventually, with the explosion of number of frameworks, consolidation is going to happen. Segun is influential enough that Zag has a good chance of being what the consolidation ends up centering around.

it's not perfect yet, but I find zagjs promising

Keep an eye on ZAG and ARK from the Chakra UI team, I feel like together with UnoCSS that could get very powerful.

🔗 Head over to https://zagjs.com/ to learn more about Zag.js and get started with building accessible UI components in your web applications!

The Zag.js documentation can be found here: https://zagjs.com/.

PrimeNg GitHub

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

PrimeNG (MIT license)

PrimeNg Release Notes

PrimeNG: Something nice about this collection is how you choose the base theme. You are presented with choosing design options that are taken from other popular design frameworks such as Material Design, Bootstrap, Soho, Fluent, Nano, and more. This is done with a visual editor, which is part of the theming options. PrimeNG also has a Figma UI kit, ready-made templates, and a SASS API.

PrimeNG is released under the MIT License https://github.com/primefaces/primeng/blob/master/LICENSE.md

We use PrimeNG which MIT licensed. It's great.

After months of hard work, we're excited to share the new major update on PrimeNG that mostly focuses on the documentation.