Glad you found a solution for now. The reason for this is that Imagemagick may be invoked in different ways depending on which installation of the program you are using.
For example, in some installations you call
directly, and specify the subcommand as an argument:
In other installations, you call the subcommands directly:
I believe that some installations also support both. It looks like the first mode of operation is not being handled on MacOS (invoking the subcommand as an argument to
. I will file a bug for this. I will also file a bug to update the node documentation with more clarification about the different ways that Imagemagick can be invoked.
Are you able to call the subcommands directly with your installation? If so, the easiest setup would be putting the Imagemagick binary folder on your system path.
Lastly, there will be some work done on the Imagemagick node to make this easier and more seamless for the user.