Support for Storybook v9

[giladgray]

Is your feature request related to a problem? Please describe.
These packages do not support Storybook 9 yet.

Describe the solution you'd like
Bump Storybook dependency to v9-compatible.

Describe alternatives you've considered
None, this is the way to do Cypress + Chromatic.

Additional context
I want to upgrade my project to SB 9 but this is holding me back. I don't want to install both v9 and v8.5 side-by-side.

[rafatairnz]

Can also confirm that this is holding us back from upgrading to v9 and we already have v10 out.
https://storybook.js.org/blog/storybook-10/

@domyen @ethriel3695

[ethriel3695]

Can also confirm that this is holding us back from upgrading to v9 and we already have v10 out.
https://storybook.js.org/blog/storybook-10/

@domyen @ethriel3695

@rafatairnz I was off last week. I'll get on this right away and get a timeline for you on upgrading. Can you email me the build logs privately so I can get additional context as well, please.

[ethriel3695]

@rafatairnz @giladgray
We are continuing to explore options here. The issue with the e2e workflow using a different version of Storybook is that it is challenging to make it work for users. If we upgrade Storybook, it works for people who have been upgraded, but then it fails for others who are still on older versions of Storybook. Until now, we haven't encountered an issue where newer versions of Storybook are incompatible with the e2e package.

@rafatairnz I was able to reproduce the error you are receiving when I added the following:

  "overrides": {
    "@storybook/addon-links": "^10.0.8",
    "@storybook/addon-onboarding": "^10.0.8",
    "@storybook/nextjs": "^10.0.8",
    "storybook": "^10.0.8"
  }

Do you have an overrides object in your package.json? That appears to cause the path[1] issue you are seeing.

[giladgray]

Until now, we haven't encountered an issue where newer versions of Storybook are incompatible with the e2e package.

If this is the case, then the blocker is the dependency versions in package.json. Can you widen the dependency strings to allow Storybook v8/v9/v10 versions of those packages?

https://github.com/chromaui/chromatic-e2e/blob/main/packages/cypress/package.json#L77-L79

[rafatairnz]

@rafatairnz @giladgray We are continuing to explore options here. The issue with the e2e workflow using a different version of Storybook is that it is challenging to make it work for users. If we upgrade Storybook, it works for people who have been upgraded, but then it fails for others who are still on older versions of Storybook. Until now, we haven't encountered an issue where newer versions of Storybook are incompatible with the e2e package.

@rafatairnz I was able to reproduce the error you are receiving when I added the following:

  "overrides": {
    "@storybook/addon-links": "^10.0.8",
    "@storybook/addon-onboarding": "^10.0.8",
    "@storybook/nextjs": "^10.0.8",
    "storybook": "^10.0.8"
  }

Do you have an overrides object in your package.json? That appears to cause the path[1] issue you are seeing.

@ethriel3695 yes when we tried we had

"overrides": {
    "storybook": "9.1.3"
}

Would @giladgray suggestion allow for more flexibility? Could we have a major release that only supports v9+ and that would gives us a clear cut from legacy and current support?

[ethriel3695]

@rafatairnz @giladgray We are continuing to explore options here. The issue with the e2e workflow using a different version of Storybook is that it is challenging to make it work for users. If we upgrade Storybook, it works for people who have been upgraded, but then it fails for others who are still on older versions of Storybook. Until now, we haven't encountered an issue where newer versions of Storybook are incompatible with the e2e package.
@rafatairnz I was able to reproduce the error you are receiving when I added the following:

  "overrides": {
    "@storybook/addon-links": "^10.0.8",
    "@storybook/addon-onboarding": "^10.0.8",
    "@storybook/nextjs": "^10.0.8",
    "storybook": "^10.0.8"
  }

Do you have an overrides object in your package.json? That appears to cause the path[1] issue you are seeing.

@ethriel3695 yes when we tried we had

"overrides": {
    "storybook": "9.1.3"
}

Would @giladgray suggestion allow for more flexibility? Could we have a major release that only supports v9+ and that would gives us a clear cut from legacy and current support?

Yes, the ultimate goal is to update the dependency range, but it's not something the team can accomplish quickly. There are several factors that contribute to updating Storybook, particularly when SB 10 is ESM-only.

If you remove the overrides, do the archive and build-archive still fail?

[rafatairnz]

@ethriel3695 Yes I can confirm that without the overrides it does work without the error I was seeing before.

[ethriel3695]

@ethriel3695 Yes I can confirm that without the overrides it does work without the error I was seeing before.

Awesome! Do you need the overrides or can you run without them for now @rafatairnz?

[rafatairnz]

@ethriel3695 we're all good for now. Thanks for looking into this.

[rafatairnz]

@ethriel3695 ran into the problem again, this time not related overrides, more about @chromatic-com/playwright
What worked this time was to use 0.13.0-f39350a-20250512235829, this is from 10/05/25, quite behind main but it does work for my use case. I'll send the reports of the failed pipelines this time.

[ethriel3695]

@rafatairnz Thank you, I'll take a look and also esaclate this to the engineering team responsible for the repository.