Ever feel like you're in a labyrinth, but instead of a Minotaur, you're being chased by DLL dependency hell?
I've lost more sleep trying to untangle this spaghetti than I care to admit.

Let's make dependencies a breeze, not a brain-twisting puzzle. Seriously, my debugger cries every time it steps into that abyss.

My Significant Other is chasing me in my dreams.

Every version of every library that isn't fully backward _and forward_ ABI compatible should be its own entry in the FS and any OS-managed DLL database. If they can't coexist that can be expressed in runtime checks, version data embedded in the persistent storage they access, or preferably constraints in the platform's dependency solver, but

1. The vast majority of libraries fulfill a role similar to openssl or jsoncpp where all of their external interactions other than the user API conform to standards and therefore multiple versions can coexist

2. The fact that binaries reference their dependencies by a string that could refer to the expected library or it could refer to the same library from 12 years ago before the author discovered local state where every single function takes one fewer arguments, and indeed that these functions are _also_ referenced with unversioned strings, is ridiculous.

Dependency hell is dominant in anything related to javascript