README: Mention Six and Sweet.js.
An example to detect nested ternary conditionals.

http://code.google.com/p/esprima/issues/detail?id=349
Vary the parsing test with and without location info.

http://code.google.com/p/esprima/issues/detail?id=343
Speed-up unary expression parsing.

The fast path for parseUnaryExpression() is to go straight to
parsePostfixExpression() function.

V8 version 3.12.19 shows 3.7% speed-up.

http://code.google.com/p/esprima/issues/detail?id=350
Add tests for the grouping operator.

These tests highlight the problem with syntax node location when the
expression contains parentheses.

http://code.google.com/p/esprima/issues/detail?id=345
Workaround for binary expressions containing group operator.

http://code.google.com/p/esprima/issues/detail?id=345
Use the editor properly with IE.

By placing CodeMirror within div instead of p, it won't throw a warning
(exception). This way we don't fall back to plain textarea anymore.

http://code.google.com/p/esprima/issues/detail?id=300
Start ChangeLog.
Speed-up unary expression parsing.

The fast path is when there is no postfix operator.

Safari 6 shows minor 3% improvement on the benchmark suite.

http://code.google.com/p/esprima/issues/detail?id=350
Revisit the parser choice in the speed comparison page.

Drop ZeParser and Narcissus, add Acorn.

http://code.google.com/p/esprima/issues/detail?id=351
Update README, preparing for 1.0.
Start the development of version 1.1.
Fix JSLint warning in the postfix optimization.

http://code.google.com/p/esprima/issues/detail?id=350
Merge branch '1.0'
Add code query to demo/parse

http://code.google.com/p/esprima/issues/detail?id=353
Modernize the corpus for the performance tests.

http://code.google.com/p/esprima/issues/detail?id=354
Use stack-based approach for parsing binary expressions.

Instead of going recursively, binary expressions are parsed using
shift-reduce strategy with a simple stack mechanism. It makes Esprima
more similar to the parser in V8 and JavaScriptCore. Also, this means
that we don't exhaust JavaScript engine's stack anymore for a really
complex expression.

Speed-up is noticeable due to the elimination of the long chain of
recursive calls. V8 3.13.7 shows at least 8% improvement.

See also the discussion in the mailing-list:
https://groups.google.com/d/topic/esprima/FqjWJc6UawA/

http://code.google.com/p/esprima/issues/detail?id=352
Also mark version 1.1 for Bower component.
Create a standard delegate to create the syntax tree.

http://code.google.com/p/esprima/issues/detail?id=355
Use the delegate to create the syntax tree.

V8 3.13 shows roughly 1% slow-down in the performance tests. This is
the price we pay to get the flexibility.

http://code.google.com/p/esprima/issues/detail?id=355