yarn run + npm scripts

[steveklabnik]

This might be a duplicate of #733 but I'm not sure.

In rust-lang/crates.io#457, we're trying to move to yarn. It's an ember app, and so relies on things like ember test to run tests.

The important part of the diff is here: https://github.com/rust-lang/crates.io/pull/457/files#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R10

That is, we have several npm scripts that, in my understanding, should be prefixed with yarn run. But on Travis, and possibly in other configurations, this seems to fail.

Am I Doing it Wrong, or is this a bug?

[Daniel15]

Are you seeing an error message?

[nodesocket]

Also reported in #782

[shri3k]

@Daniel15

error Command failed with exit code 127

is what I get when I try yarn start.

[steveklabnik]

Ah sorry, the rebase made Travis go away. If you look at the comments, @carols10cents shows an error.

On Oct 11, 2016, 22:36 -0400, Yojan Shrestha notifications@github.com, wrote:

@Daniel15 (https://github.com/Daniel15)

error Command failed with exit code 127

is what I get when I try yarn start.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#780 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AABsiqa0NJCciwUDKNGTnHNmmzx-kibJks5qzEeSgaJpZM4KUQ7o).

[FLGMwt]

Taking a look at https://yarnpkg.com/en/docs/cli/run , the usage should be yarn run blah where blah is a key in the scripts object in package.json. I don't think you want your yarn runs in the script blocks unless they need to reference other script items.

Try changing yarn run ember test in .travis.yml to yarn run test and
change "test": "yarn run ember test" in package.json to "test": "ember test" and see if that gets you closer.

[steveklabnik]

@FLGMwt that would make sense, thanks. I've pushed a commit, we'll see what travis says.

[cafreeman]

FWIW, I'm experiencing the same issue as @steveklabnik in the same context (i.e. ember commands).

For example, I have scripts in my package.json like this:

  "scripts": {
    "build": "ember build",
    "start": "ember server",
    "test": "ember try:each",
    "test:dev": "ember test --filter ESLint -i",
    "tdd": "npm run test:dev -- -s",
    "lint": "ember test --filter ESLint"
  },

npm run test will run the script located at the test key in the scripts object (i.e. ember try:each).

yarn run test does the following:

So it seems that there's a disconnect where yarn run might not be correctly accessing the .bin folder in node_modules?

FWIW, yarn run ember try:each DOES work, so it seems the issue is scoped to actually calling .bin commands from the scripts hash.

[scothis]

Seeing an similar issue. If the script in package.json is a single command it will run. If the command has arguments or is a compound command (or contains a space), the script fails with exit code 127.

[randycoulman]

This should be fixed in #809

[steveklabnik]

@randycoulman looks like it.

What's yarn's release schedule gonna look like? Any idea when that'll hit a release?

[nodesocket]

Any eta on releasing this?

[dougludlow]

@scothis same problem here:

  "scripts": {
    "start": "node server.js",
    "test": "mocha"
  },

yarn

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

npm

$ npm start

> project-name@1.0.0 start /path/to/project
> node server.js

npm runs fine, but yarn errors out. I tried yarn run start as well and got the same results. If I remove server.js from the start script, the node repl starts up just fine.

[samccone]

As stated #809 will resolve this.

Thanks everyone!