-
Notifications
You must be signed in to change notification settings - Fork 32
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
[Bug] Not working with getAbsolutePath('@storybook/addon-svelte-csf')
in Storybook 8
#174
Comments
I am not seeing this in a minimal setup. Here's a sandbox that works fine with Storybook 8 and this addon: https://stackblitz.com/edit/github-mbaaau-wqykp4?file=src%2FButton.stories.svelte Could you provide a minimal reproduction with a repo that I can check out? Here are docs on how to create a minimal reproduction locally https://storybook.js.org/docs/contribute/how-to-reproduce, alternatively you can use https://storybook.new to create a minimal reproduction in StackBlitz. Storybook sandboxes are just a given framework (in this case Svelte + Vite) with |
I ran into this issue. I found that a fix was to remove the getAbsolutePath addons: [
'@storybook/addon-svelte-csf',
getAbsolutePath('@storybook/addon-links'),
getAbsolutePath('@storybook/addon-essentials'),
getAbsolutePath('@chromatic-com/storybook'),
getAbsolutePath('@storybook/addon-interactions')
], |
This works for me as well |
getAbsolutePath('@storybook/addon-svelte-csf')
in Storybook 8
The op's issue is because he is using a monorepo called moonrepo I can confirm this is also bugged with turborepo, and the fix is the same. |
@ChrisKnightLDN Fixed my immediate issue and the server was able to start (I am also using turborepo sveltekit), but then I got a different error after the server started up: On the server:
On the client:
|
Note
This issue has a possible workaround
Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce the behavior
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots and/or logs
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: