Static build of Storybook does not load stories on default route
See original GitHub issueDescribe the bug
We are building Storybook for static deployment, ver 5.3.3
, using Typescript (ts-loader
). When accessing the root /
route (on http-server
), the app is served, route becomes http://localhost:8080/?path=/story/*
and… no stories get shown in the UI. Sadly, also no console logs or any errors are thrown. However, if the URL is updated manually to remove the *
, it picks up the first story and everything works from then on. Any ideas?
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Configure Storybook
By default, Storybook will load stories from your project based on a glob (pattern matching string) in .storybook/main.js that matches all files in...
Read more >Publish Storybook
Build Storybook as a static web application Run the following command inside your project's root directory: YARN.
Read more >CLI options - Storybook
Storybook comes with two CLI utilities: start-storybook and build-storybook . Storybook collects completely anonymous data to help us improve user experience.
Read more >Images, fonts, and assets - Storybook - JS.ORG
We recommend serving static files via Storybook to ensure that your components always have the assets they need to load. We recommend this...
Read more >Setup Storybook - JS.ORG
Storybook is a frontend workshop for building UI components and pages in ... https://storybook.js.org/docs/react/configure/overview#configure-story-loading ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@peterpeterparker
serve
specifically has problems because it seems to rewrite paths dynamically (/iframe.html
gets rewritten toiframe
).http-server
doesn’t have this problem AFAIK.@jonniebigodes maybe this is also something good for the FAQ?
Going to close this issue if you all don’t mind. A recent pull request was merged that addressed this.
Feel free to re-open regarding any follow up.
Stay safe