[Bug] Error when Story name is same as component import specifier

[xeho91]

Describe the bug

Discord thread

What is happening:
In the appendix of compiled out of Svelte component, we're creating export variable declarations whose names are based on the name prop in each <Story>.
We didn't cover the case when Story name could re-declare the import specifier of the component.

Steps to reproduce the behavior

Define a <Story> with name prop having the same as component import declaration.

[JReinhold]

Probably a duplicate of #167

This is not just a problem with imported component names, it will happen with any variable name declared in the module scope that collides with a story name.

A workaround is to use the exportName prop on Story to manually fix the collision.

https://github.com/storybookjs/addon-svelte-csf/tree/next?tab=readme-ov-file#custom-export-name

It's a tricky issue to solve, because the name/exportName of the story is used in MDX docs, where you import them by that name, so we can't just attach a hash to the variable name, as that would make it impossible to import.

[xeho91]

I have one idea in my mind. I'm not sure if this solves the problem.

Currently in the appendix we create named exports (variables).
What if we could use exports list? Example:

const __SomePrefix__Primary = __stories["Primary"];
const __SomePrefix__Secondary = __stories["Secondary"];

export {
  __SomePrefix_Primary as Primary,
  __SomePrefix_Secondary as Secondary,
}

In the case of having <Story> prop name same as component import specifier, it would look like this:

import Button from "./Button.svelte";

const __SomePrefix__Button = __stories["Button"];

export {
  __SomePrefix__Button as Button,
}

---

Concerns:

1. This possibly would affect your recent work on the issue with source maps (related to portable stories),
2. I'm unsure if Storybook internal parser(?) covers this case.