You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: Error: page.evaluate: SB_PREVIEW_API_0010 (MissingStoryFromCsfFileError):
Couldn't find story matching id 'library-2-0-animatedtypingwrapper--default' after importing a CSF file.
The Storybook was published correctly, but the Chromatic verification step was failing.
Verification could not handle subdirectories properly:
Note the "!(new)" in the components/lib section solves this and I can now finally deploy the storybook and verify it.
Without the fix Chromatic adds the story to both the top folder and the nested folder, which is probably what causes the issue.
vanessayuenn
changed the title
Customer hits error SB_PREVIEW_API_0010 due to indentation during Chromatic Extract process
error SB_PREVIEW_API_0010 due to indentation during Chromatic Extract process
May 15, 2024
@tmeasday if this works in Storybook and fails in Chromatic is it a storybook issue or a Chromatic one? I checked out the linear issue and the apps team said to escalate to Storybook. I wonder if we should just fail indexing if a component/story gets indexed by two different globs in main.js?
Describe the bug
We hit error:
The Storybook was published correctly, but the Chromatic verification step was failing.
Verification could not handle subdirectories properly:
It places all stories in components/lib under Library EXCEPT all under components/lib/new.
This works in Storybook only.
Replacing it with
Note the "!(new)" in the components/lib section solves this and I can now finally deploy the storybook and verify it.
Without the fix Chromatic adds the story to both the top folder and the nested folder, which is probably what causes the issue.
Without fix (confuses chromatic):
With fix (publish works):
To Reproduce
chromatic-issue.zip
System
N/A
Additional context
Refer to internal task: AP-4626
The text was updated successfully, but these errors were encountered: