Closed rtwk closed 7 years ago
Just observed the same error. :+1:
As side effect, the -d
option is not working too... Help is appreciated!
Other modules are affected and I'm not sure how to solve it...
-d option is working in my case. But no luck with starting it a as a child process.
Interesting! So, after doing web-term -d -p 9000
are you able to open the localhost:9000
?
No it is not accessible over http. But the daemon seems to start. At least not throwing any error message. May be you are right. It does not start at all.
Yes, no error, but it fails to start for the same reason. I think it's breaking because of the new version of Node, but don't understand why.
This is very strange. It starts when started from terminal but you call it from nodejs code as a child process and it fails.
Exactly...
Is it because new version of node or because it is rewrite in ES6
It's not because of rewrite. It makes me think it's because of the new Tilda versions (>=4.4.0):
https://github.com/IonicaBizau/tilda
There I added some process.stdin
things which are related to this behavior....
Confirming it's a bug in Tilda: https://github.com/IonicaBizau/tilda/issues/11
I'm on it.
Isolated this case: http://stackoverflow.com/q/40588859/1420197
@rtwk When you want to start it as child process, use spawno
or specify stdio: ["inherit"]
in the spawn options.
I was using web-term as child process. And it was working fine. But after updating to the latest version (node v6>), it fails to start web-term as child process. It works when started from terminal directly though.