Post #3884664

When I resolved today conflicts in `package-lock.json` I thought about the tales of "DLL hell" from the WIn32 universe and dotNet. These tales look like children scaretales compared to the pile of foo and bar the package-lock.json is. its mere existence happens only because the javascript is not compiled language into java-like or WASM-like form of single binary file per package with all its dependencies, onioned with each compilation of parent package. Is there other way to avoid package-lock?