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
I'm using storybook version alpha49 with vite plugin. When running storybook dev command storybook dev, I get following runtime error: [vite] Internal server error: Failed to resolve import "C:pathtorepo.storybookpreview.jsx" from "..\..\virtual:\@storybook\builder-vite\vite-app.js". Does the file exist? Plugin: vite:import-analysis File: /virtual:/@storybook/builder-vite/vite-app.js:16:8 14 | import('@storybook/addon-essentials/highlight/preview'), 15 | import('@storybook/addon-interactions/preview'), import('C:\path\to\repo\.storybook\preview.jsx')]) | ^ 17 | return composeConfigs(configs); 18 | }
Works fine on alpha.48
Please let me know if you need any more information or need help with reproducing
@IanVS this might be related to #19689, this seems to be a Windows-specific issue, which is why it didn't raise any error when I've tested it. Just went through a quick test on both environments, it still works fine on Linux.
EDIT: Shouldn't this line use Vite's normalizePaths function?
Describe the bug
Hello
I'm using storybook version alpha49 with vite plugin. When running storybook dev command
storybook dev
, I get following runtime error:[vite] Internal server error: Failed to resolve import "C:pathtorepo.storybookpreview.jsx" from "..\..\virtual:\@storybook\builder-vite\vite-app.js". Does the file exist?
Plugin: vite:import-analysis
File: /virtual:/@storybook/builder-vite/vite-app.js:16:8
14 | import('@storybook/addon-essentials/highlight/preview'),
15 | import('@storybook/addon-interactions/preview'),
import('C:\path\to\repo\.storybook\preview.jsx')])
| ^
17 | return composeConfigs(configs);
18 | }
Works fine on alpha.48
Please let me know if you need any more information or need help with reproducing
@storybook/cli v7.0.0-alpha.49
To Reproduce
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: