Long live esprima!
Add GitHub ribbon.
Add the BSD license file.
Package manifest.
Live demo for the parser.

http://code.google.com/p/esprima/issues/detail?id=12
Import unit tests.

This runs only in the browser so far. Command-line runner is still
not covered in this commit.

http://code.google.com/p/esprima/issues/detail?id=1
Add some benchmark tests.

For parsing corpus, several popular JavaScript libraries (with two
latest stable versions) are included: jQuery, Prototype, Ext Core.

Timing is measured using benchmarkjs.com.

http://code.google.com/p/esprima/issues/detail?id=2
Improve the speed of token lookahead.

Since it happens very often while matching different grammar rules,
cache the next token to avoid expensive re-tokenization.

Running the benchmarks suite shows massive performance improvement:

5.6x faster on Safari 5.1:
  before: 11502.5 ms
  after:   2025.4 ms

6.1x faster on Chrome 15:
  before: 14569.5 ms
  after:   2371.0 ms

5.3x faster on Firefox 8:
  before:  8046.2 ms
  after:   1500.9 ms

http://code.google.com/p/esprima/issues/detail?id=3
Improve character lookup.

peekChar() method does not have to be complicated, thus inline it wherever
it is needed.

Firefox 8 running the benchmarks suite shows 8% win.

http://code.google.com/p/esprima/issues/detail?id=13
Add command-line parser for Node.js.

http://code.google.com/p/esprima/issues/detail?id=18
Add support for labeled statement.

It is covered in ECMAScript Language Specification Section 12.12.
This also fixes parsing MooTools and JSLint code.

Running the benchmarks suite show negligible performance loss.

http://code.google.com/p/esprima/issues/detail?id=10
http://code.google.com/p/esprima/issues/detail?id=15
http://code.google.com/p/esprima/issues/detail?id=16
Compare parsing speed with other similar parsers.

Timing is using benchmarkjs.com.
Other parsers included in the comparison are:
  Narcissus from Mozilla project
  parse-js (used among others in UglifyJS)
  ZeParser

The current corpus: jQuery, Prototype.

http://code.google.com/p/esprima/issues/detail?id=14
Add more info in the README file.
Set version number.

The version info is also displayed in various test pages.

http://code.google.com/p/esprima/issues/detail?id=17
Link to known problems and future plan from the README.
Update the main index page with more info.
Better link for the wiki and issues.
Show code under test in the unit test page.

http://code.google.com/p/esprima/issues/detail?id=26
Fix falsified benchmark results.

Attach the parsed syntax tree to the global 'window' object to defeat
possible "dead code elimination" optimization.

http://code.google.com/p/esprima/issues/detail?id=27
Inline isEOF() function.

Unfortunately, modern JS engines won't show any performance change.

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