Revert node-progress back to 0.0.5 to deal with regression. Also bump http-proxy to 0.8.5, with the maxSockets regression fixed.

This commit is contained in:
Nick Martin
2012-11-19 13:06:00 -08:00
parent c1c1fd9b8f
commit 5a668893f5
2 changed files with 8 additions and 6 deletions

View File

@@ -3,7 +3,7 @@
set -e
set -u
BUNDLE_VERSION=0.2.7
BUNDLE_VERSION=0.2.8
UNAME=$(uname)
ARCH=$(uname -m)
@@ -90,17 +90,19 @@ npm install handlebars@1.0.7
npm install mongodb@1.1.11
npm install uglify-js@1.3.4
npm install clean-css@0.8.2
npm install progress@0.1.0
npm install useragent@1.1.0
npm install request@2.12.0
npm install simplesmtp@0.1.25
npm install stream-buffers@0.2.3
npm install keypress@0.1.0
npm install sockjs@0.3.4
npm install http-proxy@0.8.5
# progress 0.1.0 has a regression where it opens stdin and thus does not
# allow the node process to exit cleanly. See
# https://github.com/visionmedia/node-progress/issues/19
npm install progress@0.0.5
# 0.8.4 contains a regression w/ maxSockets support. it is fixed on
# master, and will hopefully be in 0.8.5.
npm install http-proxy@0.8.3
# pinned at older version. 0.1.16+ uses mimelib, not mimelib-noiconv
# which make the dev bundle much bigger. We need a better solution.
npm install mailcomposer@0.1.15

2
meteor
View File

@@ -1,6 +1,6 @@
#!/bin/bash
BUNDLE_VERSION=0.2.7
BUNDLE_VERSION=0.2.8
# OS Check. Put here because here is where we download the precompiled
# bundles that are arch specific.