Skip to content
Commits on Feb 7, 2016
  1. Format the code according to the style

    committed
    This is done using typescript-formatter, it can be invoked with
    `npm run format-code`.
    
    Closes gh-1466
Commits on Feb 2, 2016
  1. Fix out-of-bound error location in an invalid string literal

    committed
    When a string literal is not valid, mark the initial quote as the error
    location since it is considered the offending (illegal) token.
    
    Fixes #1457
    Closes gh-1462
Commits on Jan 30, 2016
  1. @zjmiller

    Fix shorthand object destructuring defaults in variable declarations

    zjmiller committed with
    In a variable declaration, in an object destructuring pattern, a shorthand property with a default value was being incorrectly parsed as having a false shorthand field. For example, the shorthand property in `var {a = b} = c;` was being incorrectly parsed as having a false shorthand field.
    
    Fixes #1459
    Closes gh-1458
Commits on Jan 16, 2016
  1. Tolerate unterminated if/while/for

    committed
    Fixes #1042
    Closes gh-1449
Commits on Jan 15, 2016
Commits on Jan 13, 2016
Commits on Jan 11, 2016
  1. Dependencies: update JSCS

    committed
    Closes gh-1448
Commits on Jan 10, 2016
Commits on Jan 9, 2016
  1. Travis CI: No need to update npm.

    committed
    This fixes the problem running the job with Node.js 5.
    
    Closes gh-1446
Commits on Jan 8, 2016
  1. Split the speed test between the parser and the tokenizer.

    committed
    This ensures that each speed test runs in its own process.
    
    Fixes #1444
    Closes gh-1445
  2. Update ChangeLog for 2.7.1

    committed
    Refs #1346
Commits on Dec 25, 2015
  1. Reimplement comment handling using the parser delegate

    committed
    This moves the bulk of comment handling out of the Parser class.
    
    Fixes #1434
    Closes gh-1439
Commits on Dec 24, 2015
  1. Add the support for syntax node delegator

    committed
    The third parameter to `parse()` is a callback function that is invoked
    every time the parser encounters and completes a new syntax node.
    
    An example that prints "Literal ExpressionStatement Program":
    
      var list = [];
      esprima.parse('42', {}, function (node) {
        list.push(node.type);
      });
      console.log(list.join(' '));
    
    Fixes #1113
    Closes gh-1435
Commits on Dec 18, 2015
  1. Downstream test: include JSCS.

    committed
    Fixes #1247
    Closes gh-1433
Commits on Dec 16, 2015
Commits on Dec 14, 2015
Commits on Dec 13, 2015
  1. Separate API tests

    committed
    Fixes #1422
    Closes gh-1424
  2. Move the exported entry points to the main source file

    committed
    This keeps `parser.ts` and `tokenizer.ts` only contain the respective
    class and nothing else.
    
    Fixes #1427
    Closes gh-1428
Commits on Dec 12, 2015
  1. Dependencies: update JSCS and TSLint

    committed
    Closes gh-1426
Commits on Dec 10, 2015
Commits on Dec 9, 2015
Commits on Dec 8, 2015
  1. Revamp most of the parsing code

    committed
    The bulk of the code is encapsulated in a new class, Parser. For each
    parsing function, the parameters and the return value are annotated with
    the corresponding type information. As such, the AST constructors are
    also getting the additional type information.
    
    Some outdated micro-optimizations not necesary anymore (as evidenced
    from the benchmark tests) are removed.
    
    Fixes #1410
    Closes gh-1413
Commits on Dec 4, 2015
Commits on Dec 3, 2015
Commits on Dec 2, 2015
  1. Reduce duplicated code to handle directives

    committed
    In addition, parse only expression statements as each directive consists
    of a string literal and thereby guarantees that it can't be other types
    of statements.
    
    Fixes #1404
    Closes gh-1405
Commits on Nov 30, 2015
Commits on Nov 26, 2015
Something went wrong with that request. Please try again.