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

Failure to install storybook-cli #1938

Closed
armenzg opened this issue Oct 2, 2017 · 1 comment
Closed

Failure to install storybook-cli #1938

armenzg opened this issue Oct 2, 2017 · 1 comment

Comments

@armenzg
Copy link

armenzg commented Oct 2, 2017

As mentioned on issue #1937 there's been a bad release of opencollective.
A workaround is mentioned below.

The issue seen is:

$ npm i -g @storybook/cli
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm ERR! path /usr/local/lib/node_modules/@storybook/cli/node_modules/opencollective/dist/bin/opencollective.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/@storybook/cli/node_modules/opencollective/dist/bin/opencollective.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/armenzg/.npm/_logs/2017-10-02T15_23_17_309Z-debug.log

If you install it via yarn you will get the pinned version of opencollective 1.0.3 (as indicated in yarn.lock)

yarn global add @storybook/cli
yarn global v1.1.0
[1/4] 🔍  Resolving packages...
warning [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
warning [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Installed "@storybook/[email protected]" with binaries:
      - getstorybook
✨  Done in 9.04s.

People that have their own React projects and want to include storybook can work around this issue (and others in the future) by switching to yarn and have all their dependencies pinned.

@danielduan
Copy link
Member

going to close this since it duplicates #1937

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

2 participants