[dev-server-storybook] set storySource for JS stories

[LarsDenBakker]

As reported in #1178 when writing JS stories and viewing the generated docs, the story source code is not available. To make this available we need to add a compile step which adds the storySource parameter.

[jorenbroekema]

I could probably contribute this, can you point me in the right direction?

[alangdm]

A bit of a bump to this issue, I could look into trying this too if you can point us to what needs to be changed specifically

[alangdm]

Just as a side note, I took a look at what was discussed here: open-wc/open-wc#2126

As far as I can tell, JS/TS stories currently still work, mdjs stories still don't render code

[enqueue]

We are trying to integrate stories into markdown (MDX) docs. While the stories render fine, the source code is not available for readers. Do you have any advice on how to create an integrated document? I started the example storybook from the dev-server-storybook package in this repository using npm run storybook:wc, which yields these results.

Button-mdjx-docs.stories.mdx

"Show source" is visible, but clicking on it does not show the source.

Button-mdx-docs.stories.md

Button reads "No code available" and a no parking cursor is shown.

Button.stories.js

Source code is shown, but no integration in Markdown docs.

P.S.: Sorry if if "hijacked" the wrong issue, but if I understand @alangdm 's comment correctly, they are facing the same challenge.