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
Describe the bug
When starting Storybook for the first time after a clean install of Emulsify and Compound (default components), Storybook will not start and instead return an error:
ERROR in ./components/01-atoms/images/images.stories.js 1:1762-1815
Module not found: Error: Can't resolve '../../../images/icons/' in 'components/01-atoms/images'
@ ./components/ lazy ^\.\/.*$ include: (?:\/components(?:\/(?%21\.)(?:(?:(?%21(?:^%7C\/)\.).)*?)\/%7C\/%7C$)(?%21\.)(?=.)[^/]*?\.stories\.(js%7Cjsx%7Cts%7Ctsx))$ chunkName: [request] namespace object ./01-atoms/images/images.stories.js ./01-atoms/images/images.stories
@ ./storybook-stories.js 23:11-27:5
The error seems to be related to line 8 in components/01-atoms/images/images.stories.js:
Which points to a non-existent images directory in the root of the theme. Instead, this should point to the assets/icons directory that does exist in the root of the theme.
codechefmarc
changed the title
[BUG] Error starting Storybook - image directory is incorrect
[BUG] Error starting Storybook - images/icons directory is incorrect
Jan 5, 2024
Describe the bug
When starting Storybook for the first time after a clean install of Emulsify and Compound (default components), Storybook will not start and instead return an error:
The error seems to be related to line 8 in
components/01-atoms/images/images.stories.js
:const svgIcons = require.context('../../../images/icons/', true, /\.svg$/);
Which points to a non-existent images directory in the root of the theme. Instead, this should point to the
assets/icons
directory that does exist in the root of the theme.To Reproduce
Steps to reproduce the behavior:
emulsify system install compound
npm install
npm run storybook
Expected behavior
Storybook should run without errors.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: