Okay, but let's be clear about why we're putting "modern" in quotes. Sure, pulling in half of NPM is a common way to do things currently, but it's also a very painful way to do things, currently. A "modern" dependency tree is going to cause you tons of pain, starting with having to configure your dependency tree and getting worse from there. If you use a few, small, effective dependencies, you can reasonably do a cursory code review with every upgrade, and there are other major benefits.

Don't let some drive to be "modern" cause you to use libraries that make things more difficult than using vanilla JS.

But doesn‘t that say more about modern leftpaddable frontend frameworks than about the author?

It sure does. ‘Don’t repeat yourself’ and ‘avoid NIH syndrome’ are noble goals but ‘automatically update myriad libraries from random sources on the internet and then run them’ gives me the heebie jeebies.

What this guy does sounds like a machine-doable job.

At our company we use whitesource to scan each and every build for these kind of license violations.

Nearly spat out my cereal, thanks. Funny because accurate. As a relatively new node dev, this is what keeps me awake at night.

And his comment is copy-paste from Reddit: https://old.reddit.com/r/programming/comments/ekjacu/this_is...

Slightly ridiculous that we're getting to this point :-)

A reason why I appreciate Angular: then I know (or so I think?) someone else is vetting the base dependencies.