Storybook 7 won't work as a CircleCI artifact

Storybook maintainer here :wave:
We have an interesting issue report relating to storybook as a artifact in CircleCI.
I’d love for someone at CircleCI to have a peek at it, and possible offer some suggestions.


  • When static built of storybook is saved as an artifact, it can be opened, but some query parameters get added (for authentication?).
  • sub request (ESM modules/JS code) don’t get this?
  • causing 403 responses

for ease of reference, here’s the full text of the issue reported at the storybook repository:

We are currently deploying our generated storybook files as a artifacts on circleCI so we can test our doc.

It is working well with storybook 6.x, but it is not working with storybook 7.x anymore.

The reason is the following:

  • when loading a script from the generated index.html page from the domain, we are being redirected to a AWS domain (e.g., using a url containing a bunch of query parameters so that the query can return the actual script without an actual authentication
  • some of those scripts are ESM scripts being copied as-is from the @storybook dependency files
  • since some of the storybook files are importing in a relative manner (e.g. import xyz from './some-path.mjs), it results in trying to import from that same AWS domain, but without the necessary query parameters, so we’re getting a 403

A solution would be to actually compile those ESM files and transform those paths and rely on webpack’s automatic public path handling to use the initial url of the script instead of the one after redirection.

1 Like

Thanks for posting here @ndelangen . I checked with our team, We haven’t made a change around this particular process, and the core of the issue is something to do with a change in file type from v6 - v7.

Are you starting to do any process different? Creation of the .mjs files?

Edit: We do have some people looking into ways that we’ve seen this work to share.

@ndelangen I wanted to give you a quick update - we’re looking into enabling proxying Javascript in artifacts as a way to avoid what you’re experiencing and doing a security review. I will keep you updated.

Does it mean the Playwright trace artifact will work too?

Depending on what the artifact is @unickq - do you have a link or error to share?

Edit: What we changed will fix any project that was failing to load nested JavaScript, i.e. using JavaScript modules.

@ndelangen We have added proxying javascript artifacts, and you should be good now! Let me know if you have any questions.

FYI @unickq - the change we made helped with Playwright as well

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.