Grunt Exec Command with subdirectory path not working on windows

[jharding]

Grunt Exec Command with subdirectory path not working on windows

[jharding]

What if you try node node_modules/.bin/component install?

[p0wl]

Different error message:

[johlrich]

If i execute the command in cmd (or powershell) it is working.

@p0wl Are you sure about that? I am seeing the same error on windows, but I can only execute the command by hand within powershell, it error's with the same message about . not being a command when using cmd.

Powershell cs Cmd doesn't matter when grunt-exec issues the command, they both error for me.

(Funny enough I also ran into this when building noflo-ui-server 😄)

[johlrich]

What ended up working on on both platforms was a slight variation of @jharding's suggestion node node_modules/component/bin/component install

[FlorianLoch]

You should try using \ instead of / on Windows - then it is working for me. But this doesn't work on Unix - so I am doing a case differentiation which isn't a really nice solution...

[chesleybrown]

Prepending node command before node_modules/..... worked for me, thanks @johlrich!

[andrey-skl]

Also you can use path.resolve or path.relative

var path = require("path");

exec: {
            bowerinstaller: path.relative("", "node_modules/.bin/bower-installer")+" -r --silent"
        },

[mcandre]

Could grunt-exec automatically perform path.relative translation on the first whitespace-separated token in tasks? That way, Grunt "just works" on more operating systems.

[gwicksted]

It could do this.. but then it would break in other situations (ie if "node" were specified before the path). grunt-exec has no way of knowing what is a path and what is an executable or argument. This is up to the user.