epeli/underscore.string — comment on commit 56375f4be1d287e8c271a92c9672cbb7ed5378fd
File: lib/underscore.string.js line 233
By edtsech:

I agree with you. But this project (like and underscore) doesn't use semantic versioning as well. I wanted to switch fully to SemVer and make 2.0.0 release, but something stopped me. Do you have any ideas for the best way to fix current situation? Should I release 2.0.0 or maybe replace 1.2.0 release by 2.0.0? Are there any ability to know, there are dependencies to underscore.string 1.2.0 or not, in npm projects?