The scripts get added to ./node_modules/.bin
relative to wherever you install it. So depending on your path it
may resolve the commands from the working directory of the project
without having to install the package globally.
This would be convenient in this case so you don't have to
install a bunch of stuff globally in the appveyor file, you can
just specify it in your package.json like normal and it will all
It just so happens that I add a new package and the build fails
because I forget to update the appveyor file. You then have to add
the dependency there too then your'e ok. Minor inconvenience.
I am used to having the relative location `node_modules/.bin` in my path and would love for this to be the default on AppVeyor VM images. This is especially true since I've encountered some inconsistencies between platforms/images with `yarn global add ...` package binaries/scripts not being in the path.