small medium large xlarge

Back to: All Forums  CoffeeScript
Generic-user-small
26 Oct 2011, 11:37
Torkil Grindstein (1 post)

Hi.

I was thrilled today when finally opening the CoffeeScript book. But now, five hours later I am just about giving up… I seem to be unable to install this.

My system: Fedora 15

My connection: A proxy at http://proxy.rito.no:8080

Finally, I got to install node (v0.5.5) and npm (1.0.103)

But: [developer@fedora15dev ~]$ @npm install -g coffee-script@ npm ERR! Error: socket hang up npm ERR! at CleartextStream. (http2.js:1153:25) npm ERR! at CleartextStream.emit (events.js:88:20) npm ERR! at Array.0 (tls.js:668:22) npm ERR! at EventEmitter._tickCallback (node.js:197:26) npm ERR! Report this *entire* log at: npm ERR! <http://github.com/isaacs/npm/issues> npm ERR! or email it to: npm ERR! <npm-@googlegroups.com> npm ERR! npm ERR! System Linux 2.6.40.4-5.fc15.x86_64 npm ERR! command "node" "/home/developer/local/bin/npm" "install" "-g" "coffee-script" npm ERR! cwd /home/developer npm ERR! node -v v0.5.5 npm ERR! npm -v 1.0.103 npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/developer/npm-debug.log npm not ok

And: $ npm config get proxy http://proxy.rito.no:8080/

$ env | grep -i node NODE_PATH=/home/developer/local/lib/node

$ echo $PATH /home/developer/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/developer/bin

Any ideas?

Trevor_burnham__goofy_headshot__pragsmall
26 Oct 2011, 14:20
Trevor Burnham (54 posts)

I searched the npm issue tracker for “socket hang up,” and found this issue: https://github.com/isaacs/npm/issues/1453 So it may be simply be a problem with your Node version (0.5.5, which is an older version on the unstable 0.5.x branch).

The latest Node version is 0.5.10, which is a beta for 0.6.0. Note that the book was written with 0.4.x in mind, and that many Node libraries (including the CoffeeScript command-line compiler!) haven’t been updated for 0.5/0.6 compatibility yet. So I’d recommend installing the latest stable release, 0.4.12, for now.

If that doesn’t resolve your issue, you should take it up with the npm Google Group or issue tracker, as the error output suggests. Those guys really are enormously helpful, and they’d know more about it than I would.

You must be logged in to comment