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
npx sb extract not working as expected #13561
Comments
Did it work yet? |
Nope still failing. |
Perhaps you can install puppeteer manually by hand to avoid hitting this timeout? It's slow to install. @ndelangen WDYT? |
Still times out even after manual install. |
The same issue here... It seems that there's no way to use pre-intalled puppeteer if understood #13724 correctly. |
Ran into the same issue. Strangely I resolved it by calling
This strangely worked in opposite to |
Same issue here. |
Same issue here... It's a really bad bug because i cannot use storybook composeable feature. |
There is an experimental built-in
module.exports = {
features: {
buildStoriesJson: true,
}
}; Then when you |
Taking a look at this today |
@tmeasday I'm hitting this line: storybook/lib/store/src/StoryStore.ts Line 297 in 0a5466a
can you fill me in on the background info in this? |
@ndelangen in order to call In v6 mode that happens automatically and syncronously, so it shouldn't be an issue. In v7 mode, you need to There isn't really any reason to call extract in v7 mode, seeing as a build will generate (the same) |
ZOMG!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.4.0-beta.27 containing PR #16505 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
I'm on v6.4.13 and am getting this error. I'm not opted in to v7 store mode. |
Coming back to this: I figured out I was starting to use auto generated titles. For some reason removing the explicit titles on stories caused this error to fire on our custom a11y test function which currently uses extract. |
@itwasmattgregg I will be looking at a fix to this soon. |
Regarding this: #13561 (comment) I ran into this error on I had to downgrade back to |
@stabback -- you are hitting the line "Cannot call extract() unless you call cacheAllCSFFiles() first." on the v6 store? That's surprising -- do you have a reproduction you can share? |
Unfortunately, I do not have a reproduction I can share :(. I was commenting hoping the additional context of the mix of CSF and |
@stabback can you share your |
@tmeasday Happy to continue this off the public GitHub issue, however let's be sure to post the findings back here once resolved. |
Ermahgerd!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.5.0-alpha.39 containing PR #17447 that references this issue. Upgrade today to the
|
Jiminy cricket!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.4.19 containing PR #17447 that references this issue. Upgrade today to the
|
I am on 7.1.0 and I am still facing this issue. |
I'm on 7.4.1 and still facing the same issue!! |
the way to solve this issue is to override puppeteer-core in the package.json with version I'm using pnpm so it will be
you can use |
Describe the bug
Running
npx sb extract
results in the following error:To Reproduce
Steps to reproduce the behavior:
npx sb extract
from the terminalExpected behavior
The command runs and creates a
stories.json
file.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: