reduce dependency tree

[mklabs]

It's not much, but should help a bit on this dependency tree issue #165

• remove direct references to async / underscore, pull them from grunt.util
• remove references ot ncp, no longer used in favor of fstream
• match connect / prompt deps to the exact same version than grunt's deps

on the commit we rely on currently:

• https://github.com/cowboy/grunt/blob/0ba6d4b529c8789b95886714a00ec8c7dc1fbadb/package.json

should be kept up to date whenever we change the grunt version we rely on. The idea is to match the version of the dependencies we have with the ones that are also defined as grunt's dependency.

---

Next step would be to do a pull request on both grunt plugins currently we rely on: grunt-mocha and grunt-jasmine-task. We rely on grunt 0.4.x, they rely on grunt 0.3.x. Version mismatch, npm resolves them separately. We can fix it by:

• switching back to grunt 0.3.x
• wait for grunt 0.4.x to comes out and wait for each plugin to update their grunt version.
• Do a PR to move their grunt dependency as a devDependency, if accepted by the author.

Best is probably the latter option. I can initiate the respective PRs if you wish me to do so. In the meantime, until it's hopefully accepted and published to npm, we can point our deps to one of our forks.

[mklabs]

• Getting an error at this line in the server task with the updated connect version, should change the instanceof check to be against require('http').Server.

• downgraded prompt version to match grunt one: slight change required in insight prompt, currently output:

  ==============================
  We're constantly looking for ways ... 
  ==============================
  [?] undefined
  

Otherwise, tests pass.

[sindresorhus]

Do a PR to move their grunt dependency as a devDependency, if accepted by the author.

This one ;)

[addyosmani]

Great work on getting this started, @mklabs. I agree with the direction you've taken.

I can initiate the respective PRs if you wish me to do so. In the meantime, until it's hopefully accepted and published to npm, we can point our deps to one of our forks.

Absolutely. If you have time it would be brilliant to get the rest tackled too!

[addyosmani]

Thanks @mklabs!