I just clicked the allBrowser, and download on the website, I was curious what the bundle size would be... after download, Windows Defender isolated the download with that marker.
Not a very deep dive into this... though, for the most part it should be somewhat abstracted away from your application's code.
Beyond this, the most glaring issue, is the assumption that a user may only have a single role, as opposed to possibly multiple roles.
I'm kinda meh on this... A lot of this seems to be a combination of some DOM helpers and lodash-like utilities...
Most of this would be better served with micro libraries so you can cherry pick. Some parts would be better served with the built in features of JS and DOM directly.
I'd say that it largely comes down to the fact that newer CSS features are increasingly complicated, compared to what people are used to. Many have already learned less, scss and/or stylus and rolling back those things to go to more canonical css is harder.
Beyond this, many UI toolkits have already abstracted away many of the aspects on your behalf to give you a good usability level. I absolutely love what's in the box with material-ui, and every time I have to tweak flexbox layouts by hand, if feels like pulling teeth, figuratively speaking, it just isn't pleasant in any way, shape or form.
It's all very cool, transitions, flexbox/grid, variables, imports and more... In the end, there's a certain amount of entropy to overcome, abstraction to get past and things to learn.
This also doesn't even get into the fact, that many developers turn down their noses at technologies the closer to the UI that you get. JavaScript itself to this day suffers in this way, I see it often from Java and C# developers.
definitely something to keep an eye on... for me, killer features are async loading bundles and references to additional resources (images, s/css, etc) as well as some initial html tranform for environment variable injection...
I hate how slow parcel is, but absolutely love it's in the box feature set.