tag:help.appveyor.com,2012-11-13:/discussions/suggestions/637-node_modulesbin-is-not-in-the-pathAppVeyor: Discussion 2018-10-19T08:17:07Ztag:help.appveyor.com,2012-11-13:Comment/364947652015-05-08T03:50:39Z2015-05-08T03:50:40Z./node_modules/.bin is not in the path<div><p>Don't they only get added to the path if you install with the -g
switch? AKA install as a global.</p></div>Tommy Parnelltag:help.appveyor.com,2012-11-13:Comment/364947652015-05-08T20:43:12Z2015-05-08T20:43:12Z./node_modules/.bin is not in the path<div><p>The scripts get added to <code>./node_modules/.bin</code>
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.</p>
<p>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
still resolve.</p>
<p>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.</p></div>justintag:help.appveyor.com,2012-11-13:Comment/364947652018-05-22T19:08:42Z2018-05-22T19:08:44Z./node_modules/.bin is not in the path<div><p>I am used to having the relative location <code>node_modules/.bin</code> 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 <code>yarn global add ...</code> package binaries/scripts not being in the path.</p></div>jacobq