Skip to content
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

Windows 10 hubot: Cannot load adapter flowdock #95

Open
kjata30 opened this issue Jan 24, 2017 · 5 comments
Open

Windows 10 hubot: Cannot load adapter flowdock #95

kjata30 opened this issue Jan 24, 2017 · 5 comments

Comments

@kjata30
Copy link

kjata30 commented Jan 24, 2017

Getting this error when running a clean install of hubot (from npm) using the flowdock adapter.

C:\Hubot> ./bin/hubot -a flowdock -d

[Tue Jan 24 2017 16:06:54 GMT-0500 (Eastern Standard Time)] DEBUG Loading adapter flowdock
[Tue Jan 24 2017 16:06:55 GMT-0500 (Eastern Standard Time)] ERROR Cannot load adapter flowdock - TypeError: Cannot read
property 'prototype' of undefined

project.json

"dependencies": {
"hubot": "latest",
"hubot-diagnostics": "latest",
"hubot-flowdock": "latest",
"hubot-google-images": "latest",
"hubot-google-translate": "latest",
"hubot-help": "latest",
"hubot-heroku-keepalive": "latest",
"hubot-maps": "latest",
"hubot-pugme": "latest",
"hubot-redis-brain": "latest",
"hubot-rules": "latest",
"hubot-scripts": "latest",
"hubot-shipit": "latest"
},
"engines": {
"node": "7.40",
"npm": "4.0.5"
}

python 2.7.13
node-gyp 3.5.0

@mrala
Copy link
Contributor

mrala commented Jan 25, 2017

Have you tried npm rebuild?

@kjata30
Copy link
Author

kjata30 commented Jan 25, 2017

No, but I ended up just reverting to nodejs 0.12.x and it works just fine.

@bhebing
Copy link

bhebing commented Feb 2, 2017

I do have this issue, but I'm a bit confused about versioning and node. I think I have the latest, but node -v reports as v7.4.0. I did do a rebuild.

Should I upgrade something, or actually downgrade?

@bhebing
Copy link

bhebing commented Feb 3, 2017

OK, so the versioning is clear now :)

Anyway, issue is on v7.4.0, but on the v6 LTS release.

@kjata30
Copy link
Author

kjata30 commented Feb 3, 2017

@bhebing Downgrading to node 0.12.18 solved this issue for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants