Echo JS 0.11.0

https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity

You can think of the specificity of a rule as similar to a multi-part number (A.B.C.D).

A. sum of identity selectors
B. sum of class selectors
C. sum of type selectors
D. order of rule matching the given weight

!important will override a prior directive, later !important likewise.  it should be used only as a last resort, and you should re-think your structure if you ever need it.

One comment on the use... this isn't the best way to use dotenv... the way tfa is using it is as a configuration file, not as a system environment helper.  You should combine the .env loading with your system environment and single out the environment variables you are using.  The way the it is being used will hinder use of a container or orchestration system like docker and/or kubernetes and just bypasses the intent of how .env files should work, mostly for local development.

Aside: just not a big fan of ORMs for use with scripted languages... I prefer implicit queries against the data store.  From there it's easy enough to transform to/from your typescript class/interface based structures.  In fact, with template string processors, it can be much, much cleaner and simpler to just use SQL for your queries, without the level of boilerplate or impedance that an ORM introduces in a scripted language.

Reminds me a bit of Joi, which is what I've been using for my API interface validation as a Koa extension.

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.

Best option (not mentioned) - https://materialdesignicons.com/

for material-ui: https://www.npmjs.com/package/mdi-material-ui

Did a browserAll build...

Trojan:JS/Foretype.A!ml

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.

Decent writeup... Hooks docs for React Router below.

https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/api/hooks.md

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.