-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storybook experiencing CORS issue in Gitpod #21
Comments
Hi @miclgael, I just ran a test in a Gitpod instance against this repository and wasn't able to reproduce the issue. I'll try it from a cloned/templated repository to confirm if that's related, but would you be able to send me the repo you experienced this issue in? |
@miclgael I was also unable to reproduce the issue on a cloned repository. It's very odd, as I witnessed the issue occur during our call but am unable to reproduce. |
@Decipher, Spooky! Maybe it is just my home network. I run a pi-hole so sometimes weird things can happen, though If you want to check it out anyway - I've forked, committed and pushed to a branch https://github.com/miclgael/quickstart-druxt-site-tome/tree/tutorial This was the URL to the gitpod (though I don't know it will work for you.) |
Sorry for the delay @Decipher This screenshot taken today, following all the same steps, on my same network config. No CORS error. I think this issue can be closed. Glitch in the matrix perhaps? |
Describe the bug
While using Storybook in Gitpod we experienced and issue with CORS that breaks all stories.
To Reproduce
Steps to reproduce the behavior: https://gitpod.io/#github.com/druxt/quickstart-druxt-site-tome
cd drupal && ddev composer require drupal/devel && ddev drush en devel_generate && ddev drush genc
cd nuxt && npx nuxt storybook
?path=/story/druxt-entity-node-article-view-displays--default
Expected behavior
Media
If applicable, add screenshots or video to help explain your problem.
Your Environment (please complete the following information):
N/A
Additional context
The text was updated successfully, but these errors were encountered: