Angular-cli: error “implement me” when running `ng --help` command

[IRoninCoder]

I'm using angular-cli beta.6 on windows using Visual Studio. It runs ng.cmd under the node_modules/.bin and it throws the following error as a result of "ng --help":

internal/process/stdio.js:86
        throw new Error('Implement me. Unknown stdin file type!');
        ^
Error: Implement me. Unknown stdin file type!
    at process.stdin (internal/process/stdio.js:86:15)
    at C:\apptest\myapp\node_modules\angular-cli\bin\ng:33:27
    at C:\apptest\myapp\node_modules\angular-cli\node_modules\resolve\lib\async.js:44:21
    at ondir (C:\apptest\myapp\node_modules\angular-cli\node_modules\resolve\lib\async.js:187:31)
    at C:\apptest\myapp\node_modules\angular-cli\node_modules\resolve\lib\async.js:153:39
    at onex (C:\apptest\myapp\node_modules\angular-cli\node_modules\resolve\lib\async.js:93:22)
    at C:\apptest\myapp\node_modules\angular-cli\node_modules\resolve\lib\async.js:24:18
    at FSReqWrap.oncomplete (fs.js:117:15)

Ok, so it seems to me something is not implemented yet? it's already in beta.6 so i assume there has to be something else going on?

[nosachamos]

@hanijizan the command works for me. I tried ng help, ng --help and ng -h - all work. Very strange.

[IRoninCoder]

Still the same error for ng help and ng -help.

[filipesilva]

Does that happen when not using visual studio as well?

[IRoninCoder]

Visual studio runs it using nodejs engine (version 6) and since i can successfully run other scripting tasks such as gulp and systemjs builder, then i'm confident that my environment setup is right. Just hoping to replace systemjs builder with cli to get smaller and more efficient bundles, if i could get around the error.

[filipesilva]

I'm sorry but there just isn't much I can do about running CLI commands from inside Visual Studio. Since they run outside of VS, I have to assume there's some issue with how VS handles them.

Perhaps try bringing it up with the VS team?

[ceottaki]

I know the issue has been closed already but it is not a VS issue, it is an issue of NodeJS in Windows when using process.stdin from a GUI where Windows does not provide an stdin.

I've opened another issue and a pull request to fix this.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}