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

getstorybook - connect ETIMEDOUT #3060

Closed
markpritchett opened this issue Feb 23, 2018 · 7 comments
Closed

getstorybook - connect ETIMEDOUT #3060

markpritchett opened this issue Feb 23, 2018 · 7 comments

Comments

@markpritchett
Copy link

Issue details

Receive a connect ETIMEDOUT error when trying to install storybook into project.

I am behind a corporate proxy, which could be causing issues.

Steps to reproduce

Run getstorybook

Please specify which version of Storybook and optionally any affected addons that you're running

  • storybook/cli@3.3.14

Affected platforms

  • npm 5.0.4
  • OS - Windows 8.1

Screenshots / Screencast / Code Snippets (Optional)

image

@Hypnosphi Hypnosphi added the cli label Feb 23, 2018
@Hypnosphi
Copy link
Member

I am behind a corporate proxy

You probably need to contact your admins

@danielduan
Copy link
Member

danielduan commented Feb 23, 2018

@markdalgleish You can use npm config set proxy and npm config set https-proxy to configure the proxy.

@markdalgleish
Copy link
Contributor

@danielduan I think you mean @markpritchett 😄

@markpritchett
Copy link
Author

Thanks @danielduan. npm install actually works fine for me. I can use the Angular CLI without problems (which is doing a similar thing, installing packages). I wonder whether the Angular CLI is respecting the proxy settings and getstorybook isn't?

@lucidtech
Copy link

@danielduan came here for same reasons - using react create-react-app, not angular. also have proxy and have npm config set proxy and npm config set https-proxy set. npm i works fine - but getstorybook times out with the same error as above.
Finally did npm i --save-dev @storybook/react - but I see elsewhere that this is supposedly deprecated?

@danielduan
Copy link
Member

Created a ticket, basically we don't use npm or yarn to check for dependencies. Instead, we use a library which doesn't have proxy settings configured.

@Hypnosphi
Copy link
Member

Released as 3.4.0-rc.4

@issue-sh issue-sh bot removed the merged label Mar 29, 2018
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

5 participants