I have yet to see a &quot;modern&quot; JavaScript project that wasn&#x27;t a witches brew of shitty decisions and dependency hell.<p>The last one I looked at, had an npm dependency tree like crab grass. No less than 9 copies of the same module, all different versions between 0.x and 6.x - and all that module does is parse query strings.<p>The best part was when the developer of said module release v6 changing all `var`s into `let`s and `const`s and then basically responded to people who filed bugs along the lines of &quot;fuck you not my problem&quot;.<p>The last few years have seen both JavaScript and PHP gain community powered package management tools that actively encourage this type of behaviour, and until cool-kid developers understand that they need to actually be aware of the code they&#x27;re relying on, nothing will change.