Yarn: Failed to lunch Gulp

[miton18]

node v6.7.0
npm v3.10.3
yarn v0.15.1
os: windows
Gulp is working with npm, not with yarn.

D:\USER\projets\web-proxy>"$basedir/../../Users/USER/AppData/Local/Yarn/.global/node_modules/.bin/gulp.cmd" "$@"
Le chemin d’accès spécifié est introuvable.

D:\USER\projets\web-proxy>exit $?

[verekia]

Node v6.7.0
NPM 3.10.3
Yarn 0.15.1

Same here, Yarn cannot seem to find local Gulp when I run yarn start, but npm start works fine:

$ yarn start
yarn start v0.15.1
$ "gulp test" 
sh: 1: gulp test: not found
error Command failed with exit code 127.
info Visit http://yarnpkg.com/en/docs/cli/start for documentation about this command.

$ npm start
> [email protected] start /home/verekia/[...]
> gulp test

[00:07:27] Using gulpfile ~/[...]/gulpfile.babel.js
[00:07:27] Starting 'typecheck'...

package.json:

  "scripts": {
    "start": "gulp test"
  },

[treshugart]

Getting a similar error. Seems that yarn install doesn't link transitive dependency bins into ./node_modules/.bin.

[swang]

not sure what the op is specifically referring to yarn run but there are couple issues related to it. #733 #780 #782

[jacobmischka]

This is a duplicate of #727 #733 and #735 and was fixed in #809.

[miton18]

Sorry, I will explain better, my probleme is not a package.json script like 'yarn start'
My problem appear when I:

yarn global add gulp

I can't use Gulp with the 'gulp' command.

[jacobmischka]

Oh my mistake, I saw the first comment and assumed your issue was the same. Apologies!

[ticky]

unlike npm run, yarn run doesn’t run things on the system path; from what I saw doing the work for #809, this _appears_ to be deliberate. If gulp is installed as a local dependency of your package, yarn will be able to run it from there.

[miton18]

So, I don't talk about a script runing via "npm run" or "yarn run".
I talk about gulp binary installation, I can install and lunch gulp via

npm install -g gulp && gulp

But I can't do :

yarn global add gulp && gulp

it throw :

D:\USER\projets\web-proxy>"$basedir/../../Users/USER/AppData/Local/Yarn/.global/node_modules/.bin/gulp.cmd" "$@"
Le chemin d’accès spécifié est introuvable.

D:\USER\projets\web-proxy>exit $?

[FLGMwt]

FYI #1043 should fix this for everyone until there's a real fix for linking bins better. Fun stuff with how one has to fake symlinks on Windows. 😺

[busches]

Fixed in 0.16.0 with #809, please retest.

[verekia]

Fixed for me :) Thanks!

[jesperronn]

Also for me. Thanks for a quick update. Already loving yarn!

PS. Please close issue 👍

[Snugug]

This is still an issue for me when using Travis:
https://travis-ci.org/punchcard-cms/punchcard/builds/169996168

[wyze]

@Snugug, how is your gulp dependency being installed in Travis?

[jacobmischka]

Unless I'm missing something, aren't you manually calling npm run in a lot of places? https://github.com/punchcard-cms/punchcard/blob/master/package.json#L19

[wyze]

Actually @Snugug, I don't see gulp as a direct dependency or dev dependency, so maybe your issue is possibly related to #760 and waiting on #1210 to land to fix that.

[Snugug]

Would you look at that. Wonder how that slipped through. Either way, yeah #1210 sounds like it'll resolve my issue

On Oct 24, 2016, at 11:58 AM, Neil Kistner [email protected] wrote:

Actually @Snugug, I don't see gulp as a direct dependency or dev dependency, so maybe your issue is possibly related to #760 and waiting on #1210 to land to fix that.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Snugug]

Dev dependency in package.json

On Oct 24, 2016, at 11:23 AM, Neil Kistner [email protected] wrote:

@Snugug, how is your gulp dependency being installed in Travis?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[wyze]

Going to close this as it was fixed by #809.