Unable to install due to dependency? about myth

[juliangruber]

The error about node-concat-stream can be resolved by installing git and adding it to your $PATH.

[ZoeBijl]

I'm sorry, but I don't really know what you mean. I installed git using npm install git, but don't know what to do next :X

[juliangruber]

This requires git the executable, not the node module. You can download and install git from here: http://git-scm.com/download/win. Then add it to your path: http://blog.countableset.ch/2012/06/07/adding-git-to-windows-7-path/

[ZoeBijl]

The issue still persists, is there anything I can provide or maybe try something else? I really want to give Myth a go :)

I've installed git and edited the path.

[juliangruber]

what happens when you issue the git command in your shell?

[ZoeBijl]

I get a list with commands, so that seems to be working.

[ZoeBijl]

Bump, even on a new machine I still get the same result. Seams the node-concat-stream thingy is broken or something.

Would still like to try out Myth.

This is the dependency it hangs on: https://github.com/visionmedia/node-concat-stream

I'm not even able to install that directly from there.

[juliangruber]

can you post your npm-debug.log?

[ZoeBijl]

Sure :)

http://codingkittens.com/dir/npm-debug.log

[juliangruber]

maybe update node?

[ZoeBijl]

Hmm, weird, just tried it at home at my Mac, it said it needed the Developer Tools so I installed those and then everything went OK, I can now compile and everything.

Seems to be a Windows problem. I shall update node and NPM first thing in the morning and report back here.

[damianbaar]

I really want to use myth but I'm blocked by this issue. Unfortunately I'm not able to use git and npm together because of some proxy restrictions.

As I can see, this dep is only used for command like, so is there any chance to align that dep to npm (regarding this one) or pull out handling the command line from myth and move to separate repo, like they did with grunt-cli? or just rewrite those few lines?

Thanks in advance!

[juliangruber]

pulling in @visionmedia

[tj]

damn npm, I've definitely seen this issue too, might have time to check it out today

[ianstormtaylor]

should be fixed by de3d6e3

thanks!

[damianbaar]

works like a charm, thanks for fast reaction!