Could you cut a 1.0.0 hard release and then follow normal NPM practices around major/minor/bump releases? As it is, we have to manually bump our consuming package.json to pick up any new release; it would be easier for your end users if we could just specify that we want ^1.0.0 and let semver work properly.
Could you cut a 1.0.0 hard release and then follow normal NPM practices around major/minor/bump releases? As it is, we have to manually bump our consuming package.json to pick up any new release; it would be easier for your end users if we could just specify that we want
^1.0.0
and let semver work properly.