Closed JonathanMcclennon closed 11 years ago
The reason is neglect. I have a lot of modules which I maintain and keeping all of their dependencies up to date can (a) break tests and (b) accumulates to a large portion of time.
That being said, if you open up a pull request with the package.json
changes, I will run the tests and if they pass, I will merge it in.
Lastly, npm
allows for depending on different versions of a module for different dependencies, so grunt-curl
and request
should be non-conflicting. The only issue would be more disk space. However, it is preferred to use grunt-curl
as a devDependency
rather than a normal dependency as grunt
tasks should be run only while in development.
Updated package to point to request@2.21.0
for grunt-curl@1.1.0
.
I use both grunt-curl and request, however I need to use the newest request V2.21.0, though grunt-curl comes with 2.12.0. I was just wondering if there was reason it was using an older version?