<issue_start><issue_comment>Title: add main field to package.json to set module entry point
username_0: It is a best practise to define the entry point of the module in the package.json file.
Using this module will be done by `require('grunt-wiredep')` instead of `require('grunt-wiredep/tasks/wiredep.js')`.
<issue_comment>username_0: Could someone please have a look at this pull request?
<issue_comment>username_1: I haven't seen any other grunt packages doing this. Grunt will do the requiring for you. I would say continue to use the full path, as I don't think this is a common use case (using a grunt plug-in programmatically).

// @username_2 is this a good idea?
<issue_comment>username_2: There's no point, as grunt tasks can't be normally required anyways.
<issue_comment>username_0: thanks for your feedback. I agree that it is not a common use case to use a plugin in this way.