Closed rafaelcastrocouto closed 8 years ago
I also encountered the same problem on win10
Me too~~~
+1
I just pushed some code to ignore process.stdin on Windows. I will try to test soon on a Windows PC to see if there is a nice way of handling this. Let me know if 1.8.3 allows you to work without errors.
To update:
npm install devtool -g
Good job :+1:
@rafaelcastrocouto are you running on 1.8.3?
no, i'm on 2.0.2
@rafaelcastrocouto I don't have a windows environment to try this in, can you post this question on nodejs/node gitter, Or the irc?
@mattdesl is there anyway, you can verify that 2.0.2 is acting buggy for process.stdin?
I will test on a Windows machine on Monday. 👌
Sent from my iPhone
On Apr 2, 2016, at 3:07 AM, kelvin knighton notifications@github.com wrote:
@mattdesl is there anyway, you can verify that 2.0.2 is acting buggy for process.stdin?
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub
Awesome @mattdesl
It's still buggy in 2.x ... it just don't show the error msg on load, but if you type process.stdin
in the devtool's console it will throw the error.
I encountered the same problem. This piece of code does not work.
//test.js
var readline = require('readline');
var rl = readline.createInterface({
input: process.stdin,
output: process.stdout,
terminal: true
});
rl.on('line', function(line){
console.log(line);
})
devtool test.js < input.txt
Error: Implement me. Unknown stdin file type!
Windows 7 x64 S.O. Admin rights. Node v5.10.0. npm v3.8.3. DevTool v1.9.1.
How to reproduce:
type
npm install devtool -g
then typedevtool
inside the console there will be two errors, one at line 127 and the other at line 128 at C:\Users\rafael\AppData\Roaming\npm\node_modules\devtool\node_modules\electron-prebuilt\dist\resources\atom.asar\renderer\lib\init.jsError: Implement me. Unknown stdin file type!