Whilst this is true, it's clearly bad practice to have a 'latest' dependency in any module that is itself designed to be depended upon. Personally I've never s

Whilst this is true, it's clearly bad practice to have a 'latest' dependency in any module that is itself designed to be depended upon. Personally I've never seen this be a problem in practice. Possibly because I'm lucky, possibly because I've only used dependencies that don't do this. Since I mostly use quite popular libraries, and check the dependencies of the more niche ones I decide to use for exactly things like this, I think the latter is probably the case. Out of curiosity, I wonder if anyone here has hit this problem in practice with npm and could provide a concrete example - in particular with popular open source dependencies? Yes it's a possible problem in theory, but a lot of problems in software are possible in theory but rarely occur in practice because people follow sensible patterns to guard against them.