Merge 0.1.2 bugfixes
Fix issue where .js source file is not renamed properly
Move JSHint options into an external .jshintrc file

While this is another mystery file that could conceivably confuse a user, it's the recommended way to configure JSHint, and many editors can take advantage of these settings if they live within an external file.

* Properties within `.jshintrc` have been sorted alphabetically.
* `jquery` and `browser` JSHint options have been set in .jshint, to reflect the most common JavaScript environment in WP
* `quotmark` JSHint option has been set to encourage consistency without enforcing an opinion on single- vs double-quotes
* Gruntfile itself has been edited to pass `strict` and `trailing` JSHint tests by default
Merge pull request #3 from kadamwhite/jshint-adjustments

Move JSHint options into an external .jshintrc file
Merge pull request #2 from kadamwhite/js-file-naming-issue

Fix issue where .js source file is not renamed properly.
Use separate jshint configs for our browser files and our grunt file

main difference is that browser isn't set to true but node is in the grub file
Use matchdep instead of listing each grunt task to include
Backport master
Merge pull request #4 from aaronjorbin/master

Use matchdep for loading grunt modules
Backport master