Permalink
Browse files

I actually think this should still work for Node 0.6.*.

  • Loading branch information...
1 parent d56a02b commit 7e545f2e9eb99f378645a3ad83df462420ea15b5 Dan Bornstein committed Aug 24, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 package.json
View
2 package.json
@@ -29,7 +29,7 @@
"main": "lib/ursa.js",
"engine": {
- "node": ">=0.8.0"
+ "node": ">=0.6.0"
},
"scripts": {

4 comments on commit 7e545f2

@seishun

It doesn't.

@danfuzz

What's going wrong, and on what OS and version of Node? It worked for me in my testing (on Linux, with Node 0.6.17 built from source).

@seishun

Trying to install it on Cloud9, which uses Node.js 0.6.19, results in the following error:

ERR! Error: EXDEV, link '/usr/lib/node_modules/npm/node_modules/node-gyp/legacy/tools/gyp/gyptest.pyc'

It might be an OpenShift problem, according to this thread: https://openshift.redhat.com/community/forums/openshift/node-bcrypt-module-fails-to-install

0.6.9 installs without any problems.

@danfuzz

Ok, not much I can do about it then, I think. I'd just specify ~0.6.2 as the version of Ursa. Functionally it should be the same as 0.7.0.

Please sign in to comment.