Skip to content

Commit

Permalink
Upgrade esprima to 1.2.2 from pre-1.1
Browse files Browse the repository at this point in the history
  • Loading branch information
glasser committed Oct 30, 2014
1 parent e79e04f commit 34aac45
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
1 change: 1 addition & 0 deletions History.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@
- sqlite3: 3.0.2 (from 3.0.0)
- phantomjs npm module: 1.9.12 (from 1.8.1-1)
- http-proxy: 1.6.0 (from a fork of 1.0.2)
- esprima: 1.2.2 (from an unreleased 1.1-era commit)
- openssl in mongo: 1.0.1j (from 1.0.1g)
- MongoDB: 2.4.12 (from 2.4.9)

Expand Down
7 changes: 3 additions & 4 deletions scripts/generate-dev-bundle.sh
Original file line number Diff line number Diff line change
Expand Up @@ -193,10 +193,9 @@ rm -rf node_modules/phantomjs/tmp

npm install [email protected]

# Using the formerly-unreleased 1.1 branch. We can probably switch to a built
# NPM version now. (For that matter, we ought to be able to get this from
# the copy in js-analyze rather than in the dev bundle.)
npm install https://github.com/ariya/esprima/tarball/5044b87f94fb802d9609f1426c838874ec2007b3
# XXX We ought to be able to get this from the copy in js-analyze rather than in
# the dev bundle.)
npm install [email protected]
rm -rf node_modules/esprima/test

# 2.4.0 (more or less, the package.json change isn't committed) plus our PR
Expand Down

0 comments on commit 34aac45

Please sign in to comment.