Describe the bug
When I just run storybook, it runs just fine:
start-storybook -s public -p 9009
When I build storybook as a static app:
build-storybook -s public
serve -s storybook-static -p 4000
I get no errors, it works - but each entry is nested inside itself. (See attached image.)
To Reproduce
Steps to reproduce the behavior:
(See above)
Expected behavior
build-storybook works the same as start-storybook
Screenshots

Code snippets
N/A
System:
Additional context
Any ideas?
I'm an idiot
Inception! What was the fix?
For my npm script command to run the storybook server I had:
"storybook-serve": "serve -s storybook-static -p 4000"
The "-s" arg got accidentally copied over from the "-s" option to specify the public folder for "build-storybook -s public"
The "-s" option for serve is "Rewrite all not-found requests to index.html"
Hence the "inception"...
One of the cooler bugs I've seen 馃憣
@shilman I'm getting this same bug for vue storybook. It works fine in dev mode. But production build just mirrors iteself with no contents.
Any fix?
@palerdot This was a user bug AFAIK, not a problem with Storybook per se.
@shilman Yes. serve -s is for some reason showing nested storybooks. Not an issue with storybook.
Most helpful comment
For my npm script command to run the storybook server I had:
"storybook-serve": "serve -s storybook-static -p 4000"
The "-s" arg got accidentally copied over from the "-s" option to specify the public folder for "build-storybook -s public"
The "-s" option for serve is "Rewrite all not-found requests to
index.html"Hence the "inception"...