Add a complete jshintrc

[baer]

This replaces the existing .jshintrc file with the complete one from https://github.com/jshint/jshint/blob/master/examples/.jshintrc - replacing values where needed. There are 3 intentions behind this PR.

• Updating the .jshintrc when properties are deprecated/added is much easier when you are just tracking changes in the project's repo
• This version gives visibility into what rules can be tightened or loosened as the project needs them.
• This version explicitly enumerates the rules since declarative > imperative

I also noticed that the test folder does not pass jshint. It's mostly quotation marks and line length but that may be worth fixing eventually.

[phated]

Even though jshint supports json with comments, I don't like this strategy for a .jshintrc because other libraries might parse it with JSON.parse

[jednano]

@phated that's why @sindresorhus wrote strip-json-comments

[baer]

I agree, there are some easy tools to strip comments if you need to and I think that the comments make the file more useful since some of the options (and some of the warning messages) in jshint can be a bit cryptic. It gives you something to grep against.

[sindresorhus]

Suppose you are using JSON to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your JSON parser. - Douglas Crockford, 2012

[baer]

[yocontra]

I don't think we need to fill in the defaults here, going to close this

[baer]

The reason that you may want to fill in the the defaults is that unlike some cli programs, in jshint not defining an option does not disable it, it will just run the check using it's default value. This PR shows you what you may not realize you are even checking.

[yocontra]

@baer I'm okay with the default values. Anything I want non-default is specified in the configuration file.