News for hackers. Stuff that matters.
Re:Disabling npm's progress bar yields a 2x npm install spee... by glenjamin on Wednesday January 27, 2016 @03:30AM (#10978934)
I'm with you that version ranges cause problems, but my belief is that lockfiles are a better solution.

Generally I'd use semver ranges in libraries, and then fixed versions + lockfiles for transitive deps in applications.

I suppose this is roughly equivalent to doing `:pedantic :abort` in leiningen, except you wont't have as many warning to squash - either way you have to rely on the test suite to tell you if the versions you've pegged work.

There are no comments on this comment yet.