> NPM, yarn etc drop 3) which makes it not NP hard.
A minor point, but npm peer dependencies mean that in theory it actually is NP-hard! Even if it's rarely exhibited in practice.
> NPM, yarn etc drop 3) which makes it not NP hard.
A minor point, but npm peer dependencies mean that in theory it actually is NP-hard! Even if it's rarely exhibited in practice.
Oh yeah, forgot about those.
> In the formal models of dependency resolution, the three core conditions are: 1) Root package is included, 2) Dependency closure (everything required is present) 3) Version uniqueness (at most one version per package name)
I'm curious, which formal models of package management are you referencing?