You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
events.js:170 Uncaught TypeError: this.on is not a function at webpackJsonp../node_modules/events/events.js.EventEmitter.once(events.js:170) at CallbacksRegistry.apply (C:\123proje\123NG\123YA\YA-TEST\testangular\node_modules\electron\dist\resources\electron.asar\common\api\callbacks-registry.js:47) at EventEmitter.ipcRenderer.on (C:\123proje\123NG\123YA\YA-TEST\testangular\node_modules\electron\dist\resources\electron.asar\renderer\api\remote.js:261) at emitThree (events.js:136) at EventEmitter.emit (events.js:217) ....
I asked this on Stackoverflow. But I did not get any response. Here
I could not find the cause of the error. I'm getting this error when pipe the duplex to the socket. I created another node.js instance with child-process in electron. I solved the problem this way. But was very ugly.
"The best part of this problem was helping to understand the stream concept." I hope there is a solution.
The text was updated successfully, but these errors were encountered:
events.js:170 Uncaught TypeError: this.on is not a function at webpackJsonp../node_modules/events/events.js.EventEmitter.once(events.js:170) at CallbacksRegistry.apply (C:\123proje\123NG\123YA\YA-TEST\testangular\node_modules\electron\dist\resources\electron.asar\common\api\callbacks-registry.js:47) at EventEmitter.ipcRenderer.on (C:\123proje\123NG\123YA\YA-TEST\testangular\node_modules\electron\dist\resources\electron.asar\renderer\api\remote.js:261) at emitThree (events.js:136) at EventEmitter.emit (events.js:217) ....
I asked this on Stackoverflow. But I did not get any response. Here
I could not find the cause of the error. I'm getting this error when pipe the duplex to the socket. I created another node.js instance with child-process in electron. I solved the problem this way. But was very ugly.
The text was updated successfully, but these errors were encountered: