-
Notifications
You must be signed in to change notification settings - Fork 148
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
Windows Error: Implement me. Unknown stdin file type! #42
Comments
I also encountered the same problem on win10 |
Me too~~~ |
+1 |
Commenting the lines that refer to `process.stdin` prevents the windows error messages on Experience-Monks#42
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: |
Good job 👍 |
@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
|
Awesome @mattdesl |
It's still buggy in 2.x ... it just don't show the error msg on load, but if you type |
I encountered the same problem.
|
How to reproduce:
type
npm install devtool -g
then type
devtool
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.js
Error: Implement me. Unknown stdin file type!
The text was updated successfully, but these errors were encountered: