Open bhvngt opened 2 months ago
Given @storybook/svelte
still has to support Svelte 4 until Storybook 9.0, it might limit us in what we can do with some of the warnings.
Do we know if <svelte:component this={SomeComponent} />
can be replaced with <SomeComponent />
already in Svelte 4?
Given @storybook/svelte still has to support Svelte 4 until Storybook 9.0, it might limit us in what we can do with some of the warnings.
make sense.
Going by the documentation, it appears to me that in v4
, we can replace <svelte:component this={SomeComponent} />
with <SomeComponent />
provided SomeComponent is not an expression. Here's svelte 4 example as well as an example from their tutorial where it is used for an expression
The next
version of this addon doesn't use <svelte:component>
anywhere.
Could we move this issue to https://github.com/storybookjs/storybook since the warnings comes from components inside the @storybook/svelte
package?
Describe the bug
While running
pnpm build-storybook
multiple deprecation warnings are thrown while using this addon. I understand that svelte 5 is not yet released (it looks near release going by the number of pending open issue), hence some of this are expected. Just thought of filing this as a placeholder once things settle down. Thanks for all the effort taken to product this addon.Steps to reproduce the behavior
pnpm build-storybook
Expected behavior
Build output without any warnings
Screenshots and/or logs
Environment
OSX
v18.2
pnpm 8.15.6
chrome
v128
Additional context
There is already an issue #204 filed for
<script context="module"
deprecation. Som warnings are connected to@storybook/svelte
package. Others are connected to this addon.