Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Mar 19, 2015
  1. @michaelficarra
Commits on Mar 18, 2015
  1. @michaelficarra

    fixes #1120: support ES3 static member access restriction

    michaelficarra authored committed
    Closes gh-1123
Commits on Mar 15, 2015
  1. @ikarienator

    Destructuring Binding Pattern Step #1

    ikarienator authored committed
    The easiest case for binding pattern is when cover grammar is not
    1. function, generator and method params (allow top-level default).
    2. standalone var/let/const declaration (require top-level default if
    3. catch parameters (disallow top-level default).
    Support for binding pattern in for-loops and arrow parameters is pending
    for further support of cover grammars.
    Closes #1118.
    Closes gh-1119
Commits on Mar 13, 2015
  1. Promote strict mode reserved word outside isKeyword().

    This way, isKeyword() and thereby also scanIdentifer() won't need to know
    the current strictness.
    Refs #1027
    Closes gh-1116
  2. Simplify the logic to handle unclosed block comment.

    There is no need to check for EOF here because it is implied when
    the previous while loop terminates.
    Refs #1041
    Closes gh-1115
Commits on Mar 12, 2015
  1. @mathiasbynens

    Make `testRegExp` less restrictive

    mathiasbynens authored committed
    Closes #1114
    Closes gh-1100
Commits on Mar 11, 2015
  1. Remove the compatibility tests.

    Closes #1109.
    Closes gh-1110
  2. @mathiasbynens

    Add .editorconfig

    mathiasbynens authored committed
    This makes it easier for contributors to follow encoding, line ending, indentation, and other settings.
    Closes gh-1101
Commits on Mar 9, 2015
  1. Stable version 2.1.0.

    Closes #1067.
    Closes gh-1094
Commits on Mar 7, 2015
  1. Update ChangeLog for 2.1.0.

    Refs #1067.
  2. Update ChangeLog for 1.2.5.

    Refs #1083.
  3. @mikesherov

    Change to

    mikesherov authored
    Fixes #1095
    Closes gh-1097
  4. @mikesherov
Commits on Mar 5, 2015
  1. @ikarienator @mikesherov

    Support rest parameter in arrow expression

    ikarienator authored mikesherov committed
    Refs #1011
    Refs #1012
    Closes gh-1093
  2. @ikarienator

    The test runner should create missing baseline

    ikarienator authored committed
    Closes #1082
    Closes gh-1090
Commits on Feb 28, 2015
  1. Separate the function to record a new error.

    This is extracted from PR #262.
    Refs #1042.
    Closes #1080.
Commits on Feb 24, 2015
  1. Handle ForStatement and ForInStatement with lexical declaration.

    Also, to make it explicit, constructing a lexical declaration (const or
    let) is separated from the common variable declaration (var).
    Refs #1065
  2. Formalize lexical declaration.

    This is mostly renaming so that the terms are aligned with the spec:
      ConstLetDeclaration -> LexicalDeclaration
      SourceElement -> StatementListItem
      sourceElement -> statement, sourceElements -> body
    Refs #1065
  3. @ikarienator

    Break fixture into smaller files

    ikarienator authored committed
    Splits `test.js` file into small files, with
    "`test/fixtures/{Category}/{Test Name}.{Resource Kind}.(js|json)`"
    naming convention. 7 <i>Resource Kind</i>s are used:
    1. `tree`: a JSON file representing the result of a parsing result.
    RegExps are stringified as `{}`.
    2. `tokens`: a JSON file representing the result of a tokenization
    3. `failure`: a JSON file representing an error as defined in the old
    `test/test.js` file. Field `tokenize` indicates whether the tests should
    invoke tokenizer instead of parser.
    4. `result`: a JSON file representing the result of an API test.
    5. (none): consists the original source code string of the test.js test
    6. `source`: an executable ES5 program defining a `source` variable in
    the global scope. Useful for unicode tests since escapes are visible.
    7. `run`: an executable ES5 program. Useful for API tests. The code will
    be `eval`ed and the result value is used to compare against the expected
    result of the test case.
    The migration simply names each test case with `migration_` followed by
    a number unique within the same folder.
    Closes #1025.
Commits on Feb 20, 2015
  1. @mrennie

    Tolerate unclosed block comment.

    mrennie authored committed
    Closes #1041
  2. Simplify punctuator scanning.

    Reduce the amount of repetition. Consistently use character check
    instead of character code throughout the function.
    No performance increase or regression was observed.
    Closes #1072
  3. @ikarienator

    ES6 classes support

    ikarienator authored committed
    Closes #1001
    Closes #1061
Commits on Feb 18, 2015
  1. @ikarienator

    ES6: support computed property names

    ikarienator authored committed
    Closes #1037
    Closes #1039
Commits on Feb 17, 2015
  1. @mikesherov

    Introduce rest parameters for Function Expressions and Declarations

    mikesherov authored
    Still errors on rest parameters for arrow function expressions for now as those
    are a bit more involved and require a more significant refactor.
    Refs #1011
    Closes gh-1050
  2. @mikesherov
Commits on Feb 16, 2015
  1. @btmills

    Expand property method range and loc to include params

    btmills authored committed
    Previously, the range and loc for get, set, and shorthand methods
    inside object literal properties included only the method body,
    meaning a method's parameters were outside the range of their parent
    `FunctionExpression` node. This was happening because the
    `FunctionExpression` node wasn't being created until
    `parsePropertyFunction` was called, by which point the method's
    parameters had already been parsed. This PR solves the issue by
    creating the `FunctionExpression` node as soon as it determines that
    the property is a get, set, or shorthand method, then passing the
    node into `parsePropertyFunction`.
    Closes #1029
    Closes #1040
Commits on Feb 14, 2015
Commits on Feb 9, 2015
  1. Run Travis CI tests (container-based) with Node.js 0.12 (stable) and …

    Also, remove running the tests with the old Node.js 0.8.
    Closes #1015.
Something went wrong with that request. Please try again.