node.js - How to safely rollout new npm package version with engine requirement change -
as node deprecating old buffer usages, , unfortunately i'm using in 1 of packages. i'd love rollout new version fix before late.
i rolled out version drops node < 4 support patch version number increment, , complaints breakage few hours later.
as npm install --save
includes full semver in package.json
. makes impossible deployment machines runs different version of node resolve package earlier version.
if increase minor version or major version, users face same issue after using npm install --save
.
i know user should use same version dev , production, , npm right thing them. not perfect world. there way make rollout transparent end users using npm features?
Comments
Post a Comment