feat(Storybook): Enable "buildStoriesJson" to support composition #13506

[kubijo]

Closes #13506

Enable the buildStoriesJson storybook flag so that CDS storybook can be composed

Changelog

New

• storybook: Enable the buildStoriesJson flag

[netlify]

✅ Deploy Preview for carbon-components-react ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	61ac6fa
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-components-react/deploys/64472d30a3a3820008776341
😎 Deploy Preview	https://deploy-preview-13627--carbon-components-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for carbon-elements ready!

Name	Link
🔨 Latest commit	61ac6fa
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-elements/deploys/64472d30670c33000811995f
😎 Deploy Preview	https://deploy-preview-13627--carbon-elements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[kubijo]

I have validated that the storybook build now includes a stories.json file; however, I'm getting a CORS error when trying to integrate it into our storybook instance:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://deploy-preview-13627--carbon-components-react.netlify.app/index.json. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 404.

Could somebody look into this?
I'm guessing that netlify will have some kind of settings for this kind of thing (not sure about your public production build, though)

[tay1orjones]

@kubijo The production storybook is served via GitHub Pages, which has a Access-Control-Allow-Origin header of *. So it should work there.

I added a commit to this PR to update the Netlify config to specify the same for that header. I'm not sure if it'll work on the deploy preview yet. It might need to be merged into main for it to take effect.

In either case you should be good to go 👍 Thanks for the PR!