Adding predefined YUI vars
Merge pull request #641 from davglass/yui

Adding predefined YUI vars
Fix functionparams result

It should be array in all cases.
Merge pull request #643 from medikoo/params-error

Fix functionparams result
Revert "Merge pull request #643 from medikoo/params-error"

This reverts commit ac45bf0f9a59c49c87e007be0e155a568be7857a, reversing
changes made to 4a0d7c65fc27cee72753c7a14c2809cf4db33346.

Reason: no regression test submitted with a pull request.
Fix a bug where maxparams was failing on functions with no parameters.

verifyMaxParametersPerFunction expected the result of functionparams()
to be always an array. This is a bad assumption because when there are
no parameters, this function returns nothing.

Just changing functionparams() to return empty array was breaking
some ES5 parsing code so I decided to make
verifyMaxParametersPerFunction to be aware of possible 'undefined'.

Closes GH-642.
Added tests for YUI globals.

YUI globals support was committed in
225e653b435c21b54a1875c03208a91627fc2427 and merged in without
any tests. This patch fixes that.
// block comments allowed on indented code with smarttabs

pull request for issue #547

This update allows for the following if the smarttabs option has been enabled:

	//[space]if(something) {
	//[space][tab]doSomething();
	//[space]}

... which is the result of block commenting out the following code in some text editors:

	if(something) {
	[tab]doSomething();
	}

The smarttabs regex is now doing a negative look-behind for a "//" prior to a [space][tab], and allowing it in that case.
Test cases have been updated to account for this addition as well.
Merge pull request #652 from bmharris/547_block_commented_code

Fix for issue # 547 - // block comments on indented code
Make 'indent' behaviour consistent.

When 'indent' is used as a comment it implies 'white' option. (see
L1973). This behaviour came to us as JSLint's legacy and is outside
of scope of this commit. This commit simply makes it so the 'indent'
option passed as an argument to JSHINT also implies 'white'.

Fixes GH-655.
Experiment to combine all JSHint repos into one.

It is beneficial to have all JSHint-related projects under
one repo. So I am starting this experiment to see how it
goes. I will try to combine JSHint, JSHint Next and Node
JSHint together into one happy program.
Move files to the appropriate directories.

This commit moves files to the appropriate directories and deletes
obsolete ones. There is 100% chance that test the tree at this
point is completely broken so if you find yourself at this commit
move to the later one.
Ported all expresso tests to nodeunit

Since we're merging projects we need just one tool for unit tests.
I really like nodeunit so I ported all expresso tests to nodeunit.

Also in this patch:

 * No more comma-first, even in tests.
 * Grunt instead of Make.
 * I removed all tests that were running JSHint against itself,
	 we will use 'grunt lint' instead.
Copied over JSHint Next source from jshint-next repo.

All tests passed with minor path modifications!
Added 'npm test' and travis config.
Swapped Grunt with ShellJS, fixed lint warnings.

So I decided to swap Grunt with ShellJS for two reasons:

 1. Grunt still ships with JSHint 0.5.9
 2. I will need to write build commands in future and shelljs
    has nice helpers for that.

In addition to that, I fixed all lint warnings in tests.
Moved NPM package (node-jshint) into the main repo.

This commit moves JSHint NPM pacakge into this repo. This change
will allow us to further support NPM package as a main wrapper
around JSHint.

To conform with other tests, I rewrote node-jshint tests using
nodeunit.
Updated non-Node platform wrappers for JSHint.
Added missing comments to cli.js
Added LICENSE and CONTRIBUTING. Updated README