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

unable to run storybook (probably a bigger issue than just storybook) #875

Closed
anakinjay opened this issue Oct 12, 2016 · 7 comments
Closed

Comments

@anakinjay
Copy link

BUG:
Current behavior:
After installing react storybook and attempting to execute "yarn run storybook" I get the following errors messages:

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

package.json:

{
"name": "yarnTest",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"dependencies": {
"babel": "^6.5.2",
"bootstrap": "^3.3.7",
"bulma": "^0.2.1",
"react": "^15.3.2",
"react-dom": "^15.3.2",
"redux": "^3.6.0"
},
"devDependencies": {
"@kadira/storybook": "^2.5.2"
},
"scripts": {
"storybook": "start-storybook -p 6006",
"build-storybook": "build-storybook"
}
}

Expected behavior:
storybook server starts

node version:
6.2.2

yarn version:
0.15.1

@anakinjay anakinjay changed the title unable to run storybook (probably a bigger issue) unable to run storybook (probably a bigger issue than just storybook) Oct 12, 2016
@rjmunro
Copy link
Contributor

rjmunro commented Oct 12, 2016

Might this be related to #614? Is node_modules/.bin not being set up correctly, or not added to the PATH that scripts are called with?

Or it could be #735?

@anakinjay
Copy link
Author

anakinjay commented Oct 12, 2016

Yep, seems like a dupe of #735

For what it's worth I'm also on a Mac

@AlicanC
Copy link
Contributor

AlicanC commented Oct 12, 2016

This was fixed in #809.

@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.

@busches
Copy link
Contributor

busches commented Oct 19, 2016

This was fixed in 0.16.0

yarn run storybook
yarn run v0.16.1
$ start-storybook -p 6006
=> Using default webpack setup based on "Create React App".
=> Loading custom webpack config (full-control mode).

React Storybook started on => http://localhost:6006/

 We will collect some anonymous usage stats of how you use storybook.
 See why?: https://getstorybook.io/tracking

webpack built 8190f68f135080310b03 in 6529ms

@busches
Copy link
Contributor

busches commented Dec 1, 2016

@kittens can this be closed? This was fixed back with 0.16.0.

@wyze wyze removed the needs triage label Dec 1, 2016
@wyze wyze closed this as completed Dec 1, 2016
@conmakMIT
Copy link

Hi All, I had this same problem on my PC. The end fix was actually quite different than any documentation that I found. This applied on both linux and windows.

First you need to run:

yarn run build-storybook

then your can run:

yarn run storybook

here is some documentation that could be updated:

https://storybook.js.org/basics/quick-start-guide/

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

No branches or pull requests

8 participants