develwoutacause’s avatardevelwoutacause’s Twitter Archive—№ 962

      1. Hey @npmjs module owners, if you reduce your supported engines (or include a version bump for a dependency which does), then that's a *breaking* change and should be treated as such.
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
    1. …in reply to @develwoutacause
      I think I've found at least three transitive dependency updates today which broke semver and I keep nvm install-ing different versions just to get things to install correctly. There shouldn't be enough churn in this value for it to become a problem.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -3 🙁
  1. …in reply to @develwoutacause
    Sidebar: Is there any tooling which helps ensure that a dependency version bump *doesn't* change the supported engines of a package? This applies to transitive dependencies, so is there some way to confirm that I'm not introducing a breakage for users by updating a dependency.
    On twitter.com Twitter logo develwoutacause’s avatar Mood +5 🙂
    1. …in reply to @develwoutacause
      I imagine dependency resolution logic likely makes a foolproof tool impossible, since @npmjs could pick a version with satisfies all the semver requirements **and** the user's Node version. But the engines field shouldn't be reduced in a patch or minor version anyways, so 🤷‍♂️.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂