Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn run fails on node_modules/*/.bin/ scripts #1154

Open
leebenson opened this issue Oct 17, 2016 · 5 comments
Open

yarn run fails on node_modules/*/.bin/ scripts #1154

leebenson opened this issue Oct 17, 2016 · 5 comments

Comments

@leebenson
Copy link

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

yarn run fails to load executable scripts that are local to the node_modules folder

If the current behavior is a bug, please provide the steps to reproduce.

  1. npm i -g storybook
  2. (inside a project dir) getstorybook
  3. npm run storybook <-- works fine
  4. yarn run storybook <-- bails with error

screen shot 2016-10-17 at 09 20 39

What is the expected behavior?

For scripts inside of node_modules/*/.bin/ to be available in a yarn run context

Please mention your node.js, yarn and operating system version.

yarn 0.15.1
node 6.8.1
MacOS Sierra

@rjmunro
Copy link
Contributor

rjmunro commented Oct 17, 2016

Sounds close to #614 - it seems to run without node_modules/.bin added to the PATH environment variable. Also #875 seems to be the identical bug to this.

@guitarmanvt
Copy link

IMHO, #1156 is the underlying cause: yarn is not passing the options through to the shell properly. Fix that, and this issue will also be fixed.

@joscha
Copy link

joscha commented Oct 18, 2016

Feels as if this could also be related to #1145

@rjmunro
Copy link
Contributor

rjmunro commented Oct 18, 2016

#1156 / #735 are the root cause. It seems yarn is looking for a command called "start-storybook -p 6006" rather than looking for the command "start-storybook" and giving it the arguments "-p" and "6006".

@hawkrives
Copy link

hawkrives commented Oct 18, 2016

This was fixed by #809; the fix should be in the next release.

(edit; sorry, there appear to be further issues that weren't fixed by #809.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants