Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Branch: master
Commits on Oct 29, 2012
  1. @valueof

    Moved docs from jshint.js to README and re-aligned the code.

    valueof authored
    We don't need docs in three places (site, source and README) so I
    moved them from source to README. I also realigned broken spaces
    in options declarations and removed `/*members ... */` block because
    it adds little value and is super annoying to maintain.
Commits on Oct 27, 2012
  1. @valueof
  2. @valueof

    Minor changes: made make.js executable and updated CONTRIBUTING.

    valueof authored
    You can now use make.js without explicitly specifying node:
    	./make.js test
    I removed the note about hard-tabs and jshint.js because it was no
    longer true.
  3. @valueof

    Add 'scope' property to critical errors.

    valueof authored
    Critical errors (those produced by the 'quit' function) show up
    in as well as any other errors and warnings and
    should have the same format.
    This patch adds a missing property 'scope' to such errors. It's
    always set to '(main)' since errors are unrecoverable.
    Fixes GH-714.
Commits on Oct 13, 2012
  1. @valueof

    Convert all spaces to tabs.

    valueof authored
    This commit converts all spaces to tabs. This means that if you're
    reading this message while using 'git blame' feel free to skip to
    the previous commit to find the real author.
    Sorry about that.
  2. @valueof

    Fixed stylisting warnings in JSHint wrappers.

    valueof authored
    Since I made all files to pass the same JSHint settings some
    slipped through the cracks and started failing. How embarassing.
    This patch fixes that.
  3. @valueof

    WSH: Convert numeric parameters to numbers

    valueof authored
    For some reason, WSH wrapper was passing numeric parameters as
    strings and JSHint couldn't understand them. This patch converts
    to numbers all parameters that can be converted.
    Fixes GH-671.
  4. @valueof

    Added an FAQ section to the README.

    valueof authored
    As any other open source project we have a number of questions that
    folks keep asking over and over. This FAQ will contain answers to
    such questions starting with the "How can I turn off 'mixed tabs and
    spaces' warning?".
Commits on Oct 12, 2012
  1. @valueof

    Copied CLI documentation from node-jshint

    valueof authored
    Since we're merging all repos together I need to copy some docs so that we don't lose them forever.
Commits on Oct 9, 2012
  1. @valueof

    Two spaces instead of tabs in .travis.yml.

    valueof authored
    Travis-CI thinks that we're a ruby project for some reason. Hopefully
    this will fix it.
  2. @valueof
  3. @valueof
  4. @valueof
  5. @valueof
  6. @valueof

    Moved NPM package (node-jshint) into the main repo.

    valueof authored
    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
Commits on Sep 29, 2012
  1. @valueof

    Swapped Grunt with ShellJS, fixed lint warnings.

    valueof authored
    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.
  2. @valueof
  3. @valueof

    Copied over JSHint Next source from jshint-next repo.

    valueof authored
    All tests passed with minor path modifications!
  4. @valueof

    Ported all expresso tests to nodeunit

    valueof authored
    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.
Commits on Sep 28, 2012
  1. @valueof

    Move files to the appropriate directories.

    valueof authored
    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.
Commits on Sep 26, 2012
  1. @valueof

    Experiment to combine all JSHint repos into one.

    valueof authored
    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.
Commits on Sep 25, 2012
  1. @valueof

    Make 'indent' behaviour consistent.

    valueof authored
    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.
  2. @valueof

    Merge pull request #652 from bmharris/547_block_commented_code

    valueof authored
    Fix for issue # 547 - // block comments on indented code
Commits on Sep 20, 2012
  1. @selfcontained

    // block comments allowed on indented code with smarttabs

    selfcontained authored
    pull request for issue #547
    This update allows for the following if the smarttabs option has been enabled:
    	//[space]if(something) {
    ... which is the result of block commenting out the following code in some text editors:
    	if(something) {
    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.
Commits on Sep 16, 2012
  1. @valueof

    Added tests for YUI globals.

    valueof authored
    YUI globals support was committed in
    225e653 and merged in without
    any tests. This patch fixes that.
  2. @valueof

    Fix a bug where maxparams was failing on functions with no parameters.

    valueof authored
    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.
  3. @valueof

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

    valueof authored
    This reverts commit ac45bf0, reversing
    changes made to 4a0d7c6.
    Reason: no regression test submitted with a pull request.
  4. @goatslacker

    Merge pull request #643 from medikoo/params-error

    goatslacker authored
    Fix functionparams result
Commits on Sep 12, 2012
  1. @medikoo

    Fix functionparams result

    medikoo authored
    It should be array in all cases.
Commits on Sep 11, 2012
  1. @goatslacker

    Merge pull request #641 from davglass/yui

    goatslacker authored
    Adding predefined YUI vars
  2. @davglass

    Adding predefined YUI vars

    davglass authored
Commits on Sep 3, 2012
  1. @valueof

    Fixed a bug where new max* options were not recognized.

    valueof authored
    So while publishing r11 I noticed that new max* options (maxparams,
    etc.) were not recognized when set using JSHint comments. That was
    because we forgot to update the code that checks for numeric values.
    This patch fixes that and adds a regression test (just in case).
    Will have to move r11 pointer to this commit instead of previous one.
  2. @valueof

    Better support for catch blocks.

    valueof authored
    In JavaScript, 'catch' blocks should have their own scope--just like
    functions--but we used to treat them as an ordinary blocks meaning
    that their scope was combined with the outer function (or global).
    This patch changes that by treating catch blocks as anon functions
    with a special property '(catch)' that is 'true' only for catch
    blocks. This allows us to detect undefined variables better than
    before (see GH-247).
    In IE, however, variables from the catch scope can leak into the
    outer scope. We catch one such example (GH-618):
      var e = 2;
      try {
        throw 'boom';
      } catch (e) {
        // JSHint now warns that 'e' might get overwritten in IE.
      console.log(e + 2); // 'boom2' instead of 4
    Naturally, in 'node' environment this warning disappears.
    Closes GH-618.
  3. @valueof

    Break early when { is not followed by a number.

    valueof authored
    When parsing regular expressions and encountering a '{' that is
    not followed by a number there is absolutely no reason to continue
    parsing it as if there was a number.
    Closes GH-538.
  4. @valueof

    Make our parser to be smarter about /= and regexs.

    valueof authored
    The ridiculously long regular expression that produces tokens was
    confused about differences between '/=' and regular expressions that
    start with '='. Basically it didn't know that the latter exist.
    This patch fixes the problem using the simplest (but still dumb)
    solution. It makes sure that the token for /= is not followed by
    non-whitespace characters and '/[gim]'. I hope this will catch
    most regular expressions out there.
    Closes GH-536.
Something went wrong with that request. Please try again.