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
"Couldn't find any stories in your Storybook." after upgrade to 6.4.9 #17038
Comments
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Still a regression/bug |
Apologies about the delay here, you were quite right about the recursive flag: #17252 |
¡Ay Caramba!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.5.0-alpha.19 containing PR #17252 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
Yippee!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.4.14 containing PR #17252 that references this issue. Upgrade today to the
|
Describe the bug
This worked before, but now complains it cannot find any stories anymore:
I tried simplifying, and this still does not find anything:
Explicit paths without any wildcards work though:
System
Additional context
I realized that the context builder code has changed a lot since the last version.
The final
require
string of the pattern looks like this:It looks like
recursive = false
seems wrong here.Update
I did some more experimentations and I found the
recursive
flag is indeed incorrect and makes zero sense. This worked fine before, so not sure what you changed, but it certainly messes with thestories
globs.This works:
In
@storybook/core-common/dist/cjs/utils/to-require-context.js
it now becomes:Conclusion
This worked before, but since latest update does not anymore -
'a-*/b/**/c'
However, this still works:
'a/b/**/c'
=> Since the upgrade, a double-star glob must always be the first, apparently. (But I'm not sure. I have not spent more time to find out, where it breaks off pattern and directory.)
This regression might not be intended, or maybe it is. Either way, it SHOULD be mentioned in the migration guide.
Workaround
The text was updated successfully, but these errors were encountered: