TypeError: Cannot read property 'prototype' of undefined

Question

TypeError: Cannot read property 'prototype' of undefined

blackmiaool opened this issue 8 years ago · comments

/.nvm/versions/node/v7.1.0/lib/node_modules/tty.js/node_modules/socket.io/lib/transports/websocket/hybi-07-12.js:449
Parser.prototype.proto = EventEmitter.prototype;
^

TypeError: Cannot read property 'prototype' of undefined
at Object. (/home/blackmiaool/.nvm/versions/node/v7.1.0/lib/node_modules/tty.js/node_modules/socket.io/lib/transports/websocket/hybi-07-12.js:449:42)
at Module._compile (module.js:573:32)
at Object.Module._extensions..js (module.js:582:10)
at Module.load (module.js:490:32)
at tryModuleLoad (module.js:449:12)
at Function.Module._load (module.js:441:3)
at Module.require (module.js:500:17)
at require (internal/module.js:20:19)
at Object. (/home/blackmiaool/.nvm/versions/node/v7.1.0/lib/node_modules/tty.js/node_modules/socket.io/lib/transports/websocket/index.js:7:6)
at Module._compile (module.js:573:32)

Solution:
1 Enter ~/.nvm/versions/node/v7.1.0/lib/node_modules/tty.js/node_modules/socket.io/lib/ (change v7.1.0 to your node edition or redirect it to your node folder it you don't use nvm)
2 Replace "EventEmitter = process.EventEmitter" with "EventEmitter = require('events')"
3 Save and retry.

秦世成 commented 8 years ago

+1

blackmiaool · Answer 1 · Sun Dec 04 2016 13:21:26 GMT+0800 (China Standard Time)

It would be better if you upgrade to the newest socket.io.

blackmiaool · Answer 2 · Wed Dec 07 2016 20:55:39 GMT+0800 (China Standard Time)

Seems this repo is not maintained any more. I'll focus on my own fork. https://github.com/blackmiaool/tty.js

Alexander Stuckenholz · Answer 3 · Tue Dec 27 2016 19:44:00 GMT+0800 (China Standard Time)

Any solutions on that? Also the clone of blackmaool still has the same problem. Looking forward for a fix.

Alexander Stuckenholz · Answer 4 · Tue Dec 27 2016 19:51:00 GMT+0800 (China Standard Time)

BTW: Which version do I get by "npm install tty"? This one or the clone from backmiaool? Maybe it makes sense to rename the clone to e.g. tty2 and publish it under that new name in the npm registry?

blackmiaool · Answer 5 · Tue Dec 27 2016 20:27:17 GMT+0800 (China Standard Time)

@LosWochos76 I tried to install my fork again on my linux and found it worked well. Could you check your installation of my fork?

blackmiaool · Answer 6 · Tue Dec 27 2016 20:33:28 GMT+0800 (China Standard Time)

@qeesung @LosWochos76 This problem is caused by deprecation of old style event emitter in node7. The emitter is used by the old edition of socket.io. The solution to the problem is copying the socket.io module to root directory of this module, updating the event emitter style of it, and referring it in this module. Or you can migrate the socket.io in this module to new edition.

Alexander Stuckenholz · Answer 7 · Thu Dec 29 2016 03:03:11 GMT+0800 (China Standard Time)

Sorry, but the fork does not work. Installing it with git clone https://github.com/blackmiaool/tty.js I face multiple problems:

When I start the service via with "node index.js", I et an error due to missing dependency socket.io-client. The package.json seems to miss that. But it can be fixed by installing it manually.
Now I can run the command, but opening the browser and connecting to the service throws the following error:

tty.js/tty.js/socket.io/lib/static.js:100
client.builder(transports, {
^

TypeError: client.builder is not a function

blackmiaool · Answer 8 · Thu Dec 29 2016 09:27:21 GMT+0800 (China Standard Time)

@LosWochos76 Sorry. I found the problem. You can fix it by entering socket.io directory and execute "npm install" or pulling the newest repo.

wlLeblanc · Answer 9 · Thu Dec 29 2016 18:05:58 GMT+0800 (China Standard Time)

@chjj hi I am using the term.js The is the plug-in to complex paste?

Daniel Risacher · Answer 10 · Sat Feb 11 2017 02:37:40 GMT+0800 (China Standard Time)

https://github.com/risacher/ttyx is a fork that replaces term.js with xterm.js, updates socket.io to version 1.x and updates Express to version 4.x.

Hope this helps.

小叮当的肚兜 · Answer 11 · Sat Jul 01 2017 14:26:09 GMT+0800 (China Standard Time)

god ! this have to many error, how to deal with it?

TypeError: Cannot read property 'prototype' of undefined
at Object. (/home/node_modules/socket.io/lib/store.js:35:41)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object. (/home/node_modules/socket.io/lib/manager.js:16:13)
at Module._compile (module.js:569:30)

hugywin · Answer 12 · Mon Jul 03 2017 15:17:30 GMT+0800 (China Standard Time)

@risacher TypeError: express.basicAuth is not a function

Hassan Raza · Answer 13 · Sat Jan 27 2018 01:36:56 GMT+0800 (China Standard Time)

I am facing this issue when i run command gulp serve-dev

E:\xampp\htdocs\ng-demos\modular\node_modules\karma\node_modules\socket.io\lib\store.js:35
Store.prototype.proto = EventEmitter.prototype;
^

TypeError: Cannot read property 'prototype' of undefined
at Object. (E:\xampp\htdocs\ng-demos\modular\node_modules\karma\node_modules\socket.io\lib\store.js:35:42)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at Object. (E:\xampp\htdocs\ng-demos\modular\node_modules\karma\node_modules\socket.io\lib\manager.js:16:13)
at Module._compile (module.js:635:30)

Isaac Pak · Answer 14 · Mon Jan 29 2018 06:26:52 GMT+0800 (China Standard Time)

Looks like you need to upgrade your socket.io version. Older versions use var EventEmitter = process.EventEmitter which is deprecated. You need versions that use var EventEmitter = require('events')

Marco Bortolazzo · Answer 15 · Sat Feb 03 2018 00:02:01 GMT+0800 (China Standard Time)

@hassanuos If you update socket.io to latest version you have to modify also the code (in tty.js remove io.configure(..)).
The fastest solution is to change node_modules/tty.js/package.json and set "socket.io": "0.9.19",.
Complete with npm install from tty.js path and it works.

Tarandeep Singh · Answer 16 · Tue Nov 06 2018 21:08:03 GMT+0800 (China Standard Time)

Well, i tried many solutions from all the above options. i found the real problem to be node version.
I have updated to node v10 however the application was built 3 years ago. when EventEmitter was available via process therefore a lot of old libraries were referencing it from process directly.

Also wanted to mention, i did not have issue specific to tty.js,
but it was karma not running tests with angularjs 1.

solution

remove node_modules
nvm use v5.12.0
npm i

started the app again, and it was working.

yunliang · Answer 17 · Fri Oct 25 2019 15:02:59 GMT+0800 (China Standard Time)

@hassanuos 如果将socket.io更新到最新版本，则还必须修改代码（在tty.js中，删除io.configure（..））。
最快的解决方案是更改node_modules / tty.js / package.json并设置"socket.io": "0.9.19",。从tty.js路径
完成npm install并可以正常工作。

good