This isn't exactly an issue, but I don't know where else to go for an answer.
I am taking over as a maintainer of a web site that uses grunt-include-replace v3.2.0 during it's build process. This site has node_modules checked in. I discovered that the grunt-include-replace that was committed is slightly different than what's in your repository as v3.2.0.
Is it possible that v3.2.0 changed on npm? Did you ever release multiple 3.2.0 versions?
Attached is the modified 3.2.0. and a diff against what's in your repository. Any opinions on this mystery are greatly appreciated.
I believe that this modification was to work around some problems they were having. In other words, they hacked on grunt-include-replace until it worked the way they wanted.
This isn't exactly an issue, but I don't know where else to go for an answer.
I am taking over as a maintainer of a web site that uses grunt-include-replace v3.2.0 during it's build process. This site has node_modules checked in. I discovered that the grunt-include-replace that was committed is slightly different than what's in your repository as v3.2.0.
Is it possible that v3.2.0 changed on npm? Did you ever release multiple 3.2.0 versions?
Attached is the modified 3.2.0. and a diff against what's in your repository. Any opinions on this mystery are greatly appreciated.
includereplace.from_project.js.txt modified_v3.2.0_in_project.diff.txt