Experiencing some CORS issue in `v6.0.0` while using storybook composition feature.
See original GitHub issueExperiencing some CORS issue in v6.0.0
while using storybook composition feature.
I’m adding a ref for a local storybook:
refs: {
react_components: {
title: "React Components",
url: "http://localhost:9010"
},
The local storybook works well on port 9010, but not loaded from the combined storybook
dev-tools output:
node - v14.5.0
react - v16.13.1
In addition, I would like to know if there is an option to give a path of the storybook build directory as a url of ref?
_Originally posted by @rannyeli in https://github.com/storybookjs/storybook/issues/9311#issuecomment-671426067_
Issue Analytics
- State:
- Created 3 years ago
- Reactions:16
- Comments:15 (11 by maintainers)
Top Results From Across the Web
@storybook/client-api | Yarn - Package Manager
Build bulletproof UI components faster. Build Status on CircleCI CodeFactor Known Vulnerabilities codecov License · Storybook Community Backers on Open ...
Read more >Storybook 6.0
Storybook's new developer experience starts when you install it. Storybook 6.0 comes with best practice features pre-configured.
Read more >storybookjs/storybook (Raised $170.00) - Issuehunt
`Uncaught Error: Accessing non-existent serverChannel` in v6 mode ... [Feature Request]: Support changes to `globals` when using composition.
Read more >CODE REVIEW GUIDE - OWASP Foundation
•As a peer code reviewer, to use this book you first decided on the type of ... during a code review can be...
Read more >Comparative Study of Some Online GNSS Post-Processing ...
Many applications in surveying and mapping have been made simpler and more precise due to the advent of GNSS, and thus, the demand...
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 Free
Top 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
PR is open, with a fix
I built storybook static and served the assets from a cors enabled python http server.
I was able to get the right response headers (Access-Control-Allow-Origin: *).
But I was still getting a cors issue for
stories.json
. I actually don’t see anystories.json
being generated. Is this a different issue?