Fix identical file after replacement returns 0 changed files

[webstacker]

Relates to #61

[coveralls]

Coverage remained the same at 100.0% when pulling 661f2bb on webstacker:consistent-replace-behaviour-issue-61 into 5d8e7eb on adamreisnz:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 661f2bb on webstacker:consistent-replace-behaviour-issue-61 into 5d8e7eb on adamreisnz:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 661f2bb on webstacker:consistent-replace-behaviour-issue-61 into 5d8e7eb on adamreisnz:master.

[adamreisnz]

Thanks for the PR, I will take this into account and try to merge it for the upcoming 4.0 release. Can't merge it into the current major version as some people may rely on the current functionality.

[adamreisnz]

In 4.0.0, we return a results array for each file that was processed, along with a count of number of matches and number of replacements. That should cover the use case of #61 and allow you to figure out if any replacements were made and if a file was changed or not.