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

TypeError: Cannot read property 'prototype' of undefined #369

Open
flograsso opened this issue Aug 9, 2018 · 6 comments
Open

TypeError: Cannot read property 'prototype' of undefined #369

flograsso opened this issue Aug 9, 2018 · 6 comments

Comments

@flograsso
Copy link

I Have the following error when i execute "node app" coomand

TypeError: Cannot read property 'prototype' of undefined
at Object. (C:\Users\SoporteSEM\Downloads\uptime-3.1\uptime-3.1\n
ode_modules\socket.io\lib\transports\websocket\hybi-07-12.js:442:43)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\SoporteSEM\Downloads\uptime-3.1\uptime-3.1\n
ode_modules\socket.io\lib\transports\websocket\index.js:7:6)
at Module._compile (module.js:652:30)

@yanivsetton
Copy link

I also facing with this issue, any updates regarding this?

@keshrisohit
Copy link

i am also facing the same issue.

@almgwary
Copy link

same issue, you need to upgrade the project code for latest node and socket.io version

@yanivsetton
Copy link

make sure to install mongodb and websockio global, or if you can run this as a docker container
curl -L https://github.com/IFSight/uptime/raw/master/run | sh
the docker-compose file is located under /usr/local/docker-uptime, this is the easiest method to get this running

@diveyez
Copy link

diveyez commented Dec 3, 2018

It needs to be hardcoded for patching this. Cannot be done without developmental procedures.

@Myzel394
Copy link

I'm also facing this issue 2,5 years later - any solution so far? Tried @yanivsetton but it didn't work.

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

6 participants