Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Aug 28, 2013
  1. Bump for 1.0.4.

    authored
Commits on Aug 27, 2013
  1. Minimize the payload for npm.

    authored
    Selectively choose which files to include in the module (for npm).
    The unit tests and compatibility tests are included, this makes
    installing using npat=true still work correctly.
    
    As suggested by Sindre Sorhus, using files property in package.json
    allows explicit payload manifest.
    
    https://code.google.com/p/esprima/issues/detail?id=362
Commits on Aug 17, 2013
  1. @ide

    Support escaped "]" in regexp literal character classes (ex: "/[\]/]/")

    ide authored committed
    https://code.google.com/p/esprima/issues/detail?id=442
    
    The RegExp expression parser did not handle the escape sequence "\]" within
    character classes, or any escape sequence for that matter. Once in a character
    class, the parser consumed all characters until reaching "]".
    
    This diff makes the parser always consider escape sequences, whether it is
    currently inside of a character class or not. This more closely matches the
    grammar, which looks like:
    
      RegularExpressionChar ::=
        RegularExpressionNonTerminator but not \ or / or [
        RegularExpressionBackslashSequence
        RegularExpressionClass
    
      ...
    
      RegularExpressionClassChar ::=
        RegularExpressionNonTerminator but not ] or \
        RegularExpressionBackslashSequence
    
    http://es5.github.io/#x7.8.5
    
    That is, the parser can derive RegularExpressionBackslashSequence both inside
    and outside of character classes.
    
    Test plan: Added test case to test.js and loaded it in Chrome 30 and Firefox 25.
    These browsers produce different results for `new RegExp('[\\]/]').toString()`
    so the test case dynamically computes that value.
  2. @mduvall

    Parsing empty switch contains 'cases' key

    mduvall authored committed
    SpiderMonkey and the Parser API defined 'cases' to be in the
    SwitchStatement production.
    
    https://code.google.com/p/esprima/issues/detail?id=436
Commits on Aug 10, 2013
Commits on May 17, 2013
  1. Bump for 1.0.3.

    authored
  2. @squarooticus

    Tolerant mode must accept setters with no parameter

    squarooticus authored committed
    When parsing in tolerant mode, a setter with no parameters no longer
    halts parsing but instead adds the 'Unexpected token )' error to the
    error list.
    
    https://code.google.com/p/esprima/issues/detail?id=426
Commits on May 10, 2013
  1. @Constellation
  2. @oxyc

    Fix \v being treated as v in IE < 9

    oxyc authored committed
    IE < 9 treats '\v' as 'v' instead of a vertical tab ('\x0B').
    Read more: http://mathiasbynens.be/notes/javascript-escapes
    
    https://code.google.com/p/esprima/issues/detail?id=405
  3. Fix variance unit conversion.

    authored
    This is also needed for browser-based benchmarks.
    
    https://code.google.com/p/esprima/issues/detail?id=397
  4. @oxyc

    Fix variance unit conversion.

    oxyc authored committed
    If all values are scaled by a constant, the variance is scaled by the
    square of that constant.
    
    https://code.google.com/p/esprima/issues/detail?id=397
Commits on Dec 26, 2012
  1. @Constellation
Commits on Dec 21, 2012
  1. Detect invalid syntax of catch clause without any parameter.

    authored
    The following should trigger a syntax error:
    
        try { } catch() {}
    
    http://code.google.com/p/esprima/issues/detail?id=391
Commits on Dec 15, 2012
  1. Make the benchmarks run again on Internet Explorer.

    authored
    The V8 shell workaround is not needed anymore. In fact, declaring a
    window variable like that breaks IE.
    
    http://code.google.com/p/esprima/issues/detail?id=291
  2. Mark for 1.0.2.

    authored
Commits on Nov 2, 2012
  1. @cliffano

    Fix JUnit report format for thrown error (non SyntaxError).

    cliffano authored committed
    Thrown error should also be formatted as testsuite>testcase>error,
    just like a SyntaxError, so that tools like Jenkins JUnit report
    visualisation includes the thrown error.
    
    There is no parsing performance impact since this only affects
    esvalidate error thrown per file.
    
    http://code.google.com/p/esprima/issues/detail?id=374
Commits on Oct 30, 2012
Commits on Oct 29, 2012
  1. Bump to 1.0.1.

    authored
  2. Add .npmignore file.

    authored
    This should reduce the size of the Node.js package.
    
    http://code.google.com/p/esprima/issues/detail?id=362
Commits on Oct 18, 2012
  1. esvalidate: A simple command-line syntax validator.

    authored
    It can run with either Node.js or Rhino. Two choices for the report
    format: plain text or JUnit XML.
    
    http://code.google.com/p/esprima/issues/detail?id=361
Commits on Oct 17, 2012
Commits on Oct 16, 2012
Something went wrong with that request. Please try again.