npx sb extract not working as expected
See original GitHub issueDescribe the bug
Running npx sb extract
results in the following error:
npx sb extract
info connecting to: http://localhost:57011/iframe.html
info installing puppeteer...
TimeoutError: waiting for function failed: timeout 30000ms exceeded
at new WaitTask (/Users/rniznik/.npm/_npx/37097/lib/node_modules/sb/node_modules/puppeteer-core/lib/DOMWorld.js:549:28)
at DOMWorld.waitForFunction (/Users/rniznik/.npm/_npx/37097/lib/node_modules/sb/node_modules/puppeteer-core/lib/DOMWorld.js:454:12)
at Frame.waitForFunction (/Users/rniznik/.npm/_npx/37097/lib/node_modules/sb/node_modules/puppeteer-core/lib/FrameManager.js:657:28)
at Page.waitForFunction (/Users/rniznik/.npm/_npx/37097/lib/node_modules/sb/node_modules/puppeteer-core/lib/Page.js:1141:29)
at read (/Users/rniznik/.npm/_npx/37097/lib/node_modules/sb/node_modules/@storybook/cli/dist/extract.js:30:14)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async extract (/Users/rniznik/.npm/_npx/37097/lib/node_modules/sb/node_modules/@storybook/cli/dist/extract.js:87:18)
To Reproduce Steps to reproduce the behavior:
- Go to a Storybook project
- Run
npx sb extract
from the terminal
Expected behavior
The command runs and creates a stories.json
file.
Environment Info:
System:
OS: macOS 10.15.7
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Binaries:
Node: 14.15.1 - ~/.nvm/versions/node/v14.15.1/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.8 - ~/.nvm/versions/node/v14.15.1/bin/npm
Browsers:
Chrome: 87.0.4280.88
Edge: 87.0.664.66
Firefox: 84.0.1
Safari: 14.0.2
npmPackages:
@storybook/addon-a11y: ^6.1.11 => 6.1.11
@storybook/addon-actions: ^6.1.11 => 6.1.11
@storybook/addon-controls: ^6.1.11 => 6.1.11
@storybook/addon-docs: ^6.1.11 => 6.1.11
@storybook/addon-storysource: ^6.1.11 => 6.1.11
@storybook/addon-viewport: ^6.1.11 => 6.1.11
@storybook/addons: ^6.1.11 => 6.1.11
@storybook/react: ^6.1.11 => 6.1.11
@storybook/source-loader: ^6.1.11 => 6.1.11
@storybook/theming: ^6.1.11 => 6.1.11
@storybook/web-components: ^6.1.11 => 6.1.11
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 3 years ago
- Comments:23 (14 by maintainers)
Top Results From Across the Web
`npx sb extract` returns Error: Browser is not downloaded. ...
`npx sb extract` returns Error: Browser is not downloaded. Run "npm install" or "yarn install" #15004 ; Describe the bug Running npx extract...
Read more >How to troubleshoot storybook not loading stories?
The main.js in your ./storybook folder contains the line stories: ['../src/**/*.stories.jsx?'], since your story is named ...
Read more >storybook failed to fetch dynamically imported module
I'm trying to upgrade Storybook to the latest version 6.2.8. Had multiple issues upgrading through yarn upgrade so the final solution was to...
Read more >Advances in extraction methods, chemical constituents ... - NCBI
2 Technologies to extract volatile oil from Acorus calamus var. ... its brain activity can help us solve the problem of drug delivery...
Read more >Create Card component story using Storybook with Nuxt
Then I configured Storybook in nuxt.config.js for it to work with Nuxt. ... "storybook": "npx nuxt storybook", "deploy:sb": "rm -rf storybook-static && nuxt ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m on v6.4.13 and am getting this error. I’m not opted in to v7 store mode.
Ran into the same issue. Strangely I resolved it by calling
sb extract
from the root of the repository with the dist folder as a parameter:This strangely worked in opposite to
cd dist/storybook/your-lib/ && sb extract
in my case.