4 ms·
It looks like the major problem was that NPM updated an inrelated package, despite a lock file. I would classify this as rather unexpected behaviour. I don’t se
by bouke 8y ago
It looks like the major problem was that NPM updated an inrelated package, despite a lock file. I would classify this as rather unexpected behaviour. I don’t see why that’s relevant to dependency resolution in situations where there’s no lock file.
- hinkley 8y agoUnexpected in the sense of unwanted? Yes. Unexpected in the sense of “oh my puppy chewed up the table leg”? No, this is pretty much expected behavior from npm. Unfortunately Yarn has a bug in it that I don’t know how to fix. There’s a lot of stuff going on in both code bases and I can’t help but feel like they’ve exceeded their intrinsic complexity via coupling, and that’s why people are struggling to get them to behave correctly. I wonder if splitting this job up into separate tasks and working on them separately would net some sanity.
- twic 8y agoThe fix for this problem is not a whole new philosophy of version selection, it's being more sensible in implementing the current one. Do any of Yarn, Bundler, or Cargo have this behaviour?
- felixfbecker 8y agoYarn has the same issue (it used to do shallow updates, but this was changed due to community demand, and now theres the demand to change it back again)