If I wanted to point out what the greatest mistake in the conception of the NodeJS package manager—npm—is, its 'original sin', if you will, is the conceit that

If I wanted to point out what the greatest mistake in the conception of the NodeJS package manager—npm—is, its 'original sin', if you will, is the conceit that SemVer ('semantic versioning', a great idea in itself) is 100% reliable and that, therefore, it would be heretic or contradictory for a single module or sub-package in a project to ever want to `require()` two distinct versions of a module, say, xyz@1.0.1 and xyz@1.2.0. This is now fixed[1] but the developers stubbornly refused to see the occasional necessity of doing just this for many years. [1](https://medium.com/weekly-webtips/how-to-install-multiple-versions-of-the-same-package-in-npm-71c29b12e253 https://medium.com/weekly-webtips/how-to-install-multiple-ve...)