Comment by morgante 11 years ago A version can't be republished. 2 comments morgante Reply michaelmior 11 years ago True, but it's common to have requirements of the form "^1.0.0" (especially since this is the default of npm i --save). It's easy to publish a new version that would be installed by a project declaring a dependency in this form. morgante 11 years ago Yes, but it's trivial to pin your dependencies exactly. That's not a reason to avoid small modules.
michaelmior 11 years ago True, but it's common to have requirements of the form "^1.0.0" (especially since this is the default of npm i --save). It's easy to publish a new version that would be installed by a project declaring a dependency in this form. morgante 11 years ago Yes, but it's trivial to pin your dependencies exactly. That's not a reason to avoid small modules.
morgante 11 years ago Yes, but it's trivial to pin your dependencies exactly. That's not a reason to avoid small modules.
True, but it's common to have requirements of the form "^1.0.0" (especially since this is the default of npm i --save). It's easy to publish a new version that would be installed by a project declaring a dependency in this form.
Yes, but it's trivial to pin your dependencies exactly. That's not a reason to avoid small modules.