Hacker News new | past | comments | ask | show | jobs | submit login

> Oh, if it only was that easy. You don't control all the instances of left-pad you include (because indirect dependencies), so pinning it in your project is far from enough.

Yes, lets scrap the entire thing just because we cannot deep-pin individual dependencies. How about adding support for deep-pinning individual dependencies instead?

> re-solved by PIP and gems

Afaik, those two don't solve the problem. If within project P, dependency A depends on C v1 and dependency B depends on C v2, they just can't resolve that conflict. Which is a non-starter for tiny modules.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: