grunt-shell | Run shell commands | Command Line Interface library

I figured this is less of a nodejs problem but a unix shell issue which nodejs could avoid.

The issue is sh doesn't support brace expansions, bash does. On my Mac, sh is symlink to bash and ubuntu (18.04) sh is symlink to dash (by the results this obviously doesn't support brace expansion).

Solution is to pass {shell: '/bin/bash'} for brace expansion to work in unix systems instead of the default '/bin/sh' shell.

example using NodeJS exec function: `exec('cp ./app/images/{.png,.jpg,*.ico} tmp/images', {shell: '/bin/bash'})

example using grunt-shell

Try:

The issue ended up not being related to OS update, but rather a custom Jekyll plugin that was causing the issue. Once the plugin was removed everything worked. However, something did change perhaps in Jekyll or elsewhere to make the plugin not work all of the sudden. I will open a separate issue to figure that out. Thanks @Casper and @JoostS for quick responses.

You could consider using the grunt-shell custom-callback feature to capture the responses and handle any conditional logic.

The following example gist when running $ grunt via your command line will perform the following:

1. Change directory to a folder named quux in the projects root directory. If the folder named quux exists the following will be logged:

   Done: Successfully changed to directory 'quux'

2. However, if a folder named quux does not exist in the projects root directory the following will be logged:

The folder named 'quux' is missing

1. Subsequently the shell:create_folder Task is run, which upon creating the folder named quux logs:

Successfully created folder named 'quux'

Finally the shell:go_to_folder Task is run, which then reports point 1 above.

Gruntfile.js

Thanks to Mads Kristensen for pointing to his 2 year old blogpost - turns out VS was using a different version of the tools compared to the command prompt.

https://blogs.msdn.microsoft.com/webdev/2015/03/19/customize-external-web-tools-in-visual-studio-2015/

Your test won't work because grunt-shell runs a child_process and your callback runs after it ends and under the main process.
Same thing would happen with cross-env.

If you want to pass an environment variable to grunt-shell, you should use the options configuration according to the documentation.
For example:

With extglob (and globstar) the following syntax is correct the other [^..] is a negative character set.

I just ran into the same problem this morning with my own build. It would appear that the authors of gulp-sourcemaps added a scoped dependency to their package.json two days ago. I'm not familiar with scoped dependencies, but it would appear that's what causing npm install to fail. I am on an older version of npm that doesn't have support for scoped dependencies, but it looks like you're on a newer version - it could be that they haven't published the dependency yet, or set it public since scoped dependencies default to private.

As a short-term fix, you can do as I did, and remove the ^ from your version specifier for gulp-sourcemaps in your own package.json, which will avoid pulling the latest version of gulp-sourcemaps that has the new scoped dependency.

The short answer... It's not possible for grunt-reporter by itself to hide logs generated by a grunt-shell command.

The long answer including workaround... The logs from a grunt-shell command are generated by the shell/bash command itself and not via a node package/script. The examples shown on the grunt-reporter homepage are intercepting/manipulating a message from a node package written to stdout.

Consider the following...