Fix for tokenizing and regex

When running tokenize on code with regular expression literals
the order of tokens would sometimes be off and extra tokens inserted.
This was due to peek being called before scanRegExp finished adding
the literal to extra.tokens.

http://code.google.com/p/esprima/issues/detail?id=446
Add manifest file for component.io.

https://code.google.com/p/esprima/issues/detail?id=459
Ensure consistent library version across different files.

https://code.google.com/p/esprima/issues/detail?id=470
Remove spurious trailing comma.

https://code.google.com/p/esprima/issues/detail?id=417
Use ESLint to lint the code.

https://code.google.com/p/esprima/issues/detail?id=473
esparse should handle regular expression literals.

As suggested by Arian Stolwijk.

https://code.google.com/p/esprima/issues/detail?id=468
Use `HexIntegerLiteral`s for Unicode code points

When referring to Unicode code point values, it’s easier to stick to
hexadecimal notation. This patch makes sure we do it consistently.

https://code.google.com/p/esprima/issues/detail?id=477
Present diffs for mismatched actual and expected JSON.

https://code.google.com/p/esprima/issues/detail?id=478
Update some files in the benchmark corpus.

Updated libraries:
  - AngularJS 1.2.5
  - Backbone 1.1.0

https://code.google.com/p/esprima/issues/detail?id=354
Add "--strict-json" flag to tools/generate-test-fixture.js

Currently tools/generate-test-fixture.js outputs JSON objects whose keys are not
double-quoted. This changes the tool to accept a `--strict-json` argument which
indicates that it should always double-quote object keys.

This is useful for piping the output of generate-test-fixture.js to other
tools that expect valid JSON.

https://code.google.com/p/esprima/issues/detail?id=461