You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once I deployed my changes where your addon is upgraded and in storybook v6.5.9, I was unable to view the standalone MDX documentation I created for my tokens. It works fine in dev, but when i build storybook to be deployed, there is no design-tokens.source.json artifact in my dist/storybook/ directory and I receive a 404 on the request at the deployed location. Is this call always meant to be external? Should the bundle be providing the file on that request? 🤔
The text was updated successfully, but these errors were encountered:
Ok so, digging into this, I'm not sure if it's something you need to change or something the storybook team should change. It turns out that passing --quiet to the build-storybook command suppresses the generation of that design token file. It definitely shouldn't, but it does. At least now you're aware, and you can close this issue if you think it's not an issue with your addon. 😁
Once I deployed my changes where your addon is upgraded and in storybook v6.5.9, I was unable to view the standalone MDX documentation I created for my tokens. It works fine in dev, but when i build storybook to be deployed, there is no
design-tokens.source.json
artifact in mydist/storybook/
directory and I receive a 404 on the request at the deployed location. Is this call always meant to be external? Should the bundle be providing the file on that request? 🤔The text was updated successfully, but these errors were encountered: