New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error after updating to 0.1.8 #178

Closed
frytaz opened this Issue Sep 2, 2013 · 4 comments

Comments

Projects
None yet
4 participants
@frytaz
Copy link

frytaz commented Sep 2, 2013

npm update -g ungit
ungit
After this update all i can see is this error in browser
{
"error": "Object # has no method 'setTimeout'",
"errorType": "TypeError",
"stack": "TypeError: Object # has no method 'setTimeout'\n at Object.handle (/usr/local/lib/node_modules/ungit/source/server.js:65:7)\n at next (/usr/local/lib/node_modules/ungit/node_modules/express/node_modules/connect/lib/proto.js:190:15)\n at Object.noCache as handle\n at next (/usr/local/lib/node_modules/ungit/node_modules/express/node_modules/connect/lib/proto.js:190:15)\n at Object.handle (/usr/local/lib/node_modules/ungit/source/server.js:51:4)\n at next (/usr/local/lib/node_modules/ungit/node_modules/express/node_modules/connect/lib/proto.js:190:15)\n at Object.expressInit as handle\n at next (/usr/local/lib/node_modules/ungit/node_modules/express/node_modules/connect/lib/proto.js:190:15)\n at Object.query as handle\n at next (/usr/local/lib/node_modules/ungit/node_modules/express/node_modules/connect/lib/proto.js:190:15)"
}

@Pixy

This comment has been minimized.

Copy link

Pixy commented Sep 2, 2013

I just had the same problem, updating NPM resolved the problem for me :
http://theholmesoffice.com/node-js-fundamentals-how-to-upgrade-the-node-js-version/

Just do :
sudo npm cache clean -f
sudo npm install -g n
sudo n stable
ungit

It should work

@frytaz

This comment has been minimized.

Copy link

frytaz commented Sep 2, 2013

Yes, updating npm resolved this error, thanks :)

@rchod

This comment has been minimized.

Copy link

rchod commented Sep 3, 2013

when i do $ n stable i got this

  install : 0.10.17

  Error: invalid version 0.10.17
@FredrikNoren

This comment has been minimized.

Copy link
Owner

FredrikNoren commented Sep 4, 2013

@rchod hm no idea why that wouldn't work. Did you clean out the cache and everything before?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment