Storybook 10 support

[Sidnioulz]

Storybook 10 support

Hi there! 👋

Note

Specifically for you: your package wasn't picked up by our automation because it doesn't contain the storybook-addon NPM keyword and is not named storybook-addon-*.
I suggest adding the keyword so you can be referenced on https://storybook.js.org/addons and receive major update notifications in the future!

The Storybook team is excited to announce that Storybook 10.0.0 is coming soon with one major breaking change: Storybook is switching to ESM-only! For addons, this means simpler build scripts and an easier maintenance going forward.

What's changing?

The key changes that affect addon authors are:

1. Addon build scripts must output ESM-only
2. Some files in your addon repository must be changed to support ESM-only

What do you need to do?

1. Review the addon migration guide
2. Adjust your repository following the guide's recommendations
3. Update your addon's dependencies:

{
  "peerDependencies": {
    // Keep it at *.0.0 for broader compatibility
    "storybook": "^10.0.0"
  },
  "devDependencies": {
    // You can also use 'next' if you always want to use prereleases
    "storybook": "^10.0.0"
  }
}

4. Test your addon with the prerelease version:

npm install --save-dev storybook@next

Need help?

• Join the #addons channel on the Storybook Discord for support
• Report any issues here

Please let us know if you plan to support Storybook 10 or if you need any assistance with the migration. Your addon is an important part of the Storybook ecosystem and we're here to help! 🙏

If you don't have time to update your addon to Storybook 10, please consider finding coworkers or contributors who can help you maintain it. The storybook-community can provide support to contributors who volunteer to take over unmaintained addons.

---

This issue was created as part of our outreach to help the addon ecosystem upgrade to Storybook 10. If you have any feedback about this process or would like to opt-out from future outreach, please let us know on Discord.

[Tobbe]

@Sidnioulz Thank you for taking the time to also file the issue over here.

A quick question: Is the keyword storybook-addon (as you wrote), or storybook-addons (plural, as noted in https://storybook.js.org/docs/addons/writing-addons#integration-catalog-metadata)?

[Sidnioulz]

@Sidnioulz Thank you for taking the time to also file the issue over here.

A quick question: Is the keyword storybook-addon (as you wrote), or storybook-addons (plural, as noted in https://storybook.js.org/docs/addons/writing-addons#integration-catalog-metadata)?

Both work, we'll be changing it to storybook-addon by default starting in SB 10 :)

[Tobbe]

Figured I'd update here with what the plan is for SB 10

CedarJS currently is CJS+ESM, and supports projects that are CJS only. So we can't upgrade to SB 10 yet.

ESM support for Cedar apps is currently available as an experimental flag. As far as timelines go I'm hoping to have ESM out in a stable version before the end of the year.
After that I can look at moving to SB 10.

Priority probably looks something like this for me personally. But if someone were to sponsor me on a specific task priorities could change.

1. ESM
2. Node 24
3. Vite 7
4. Prisma 6
5. SB 10
6. React 19

[Tobbe]

@Sidnioulz Both my Node 22 upgrade PR (#511) and my Node 24 upgrade PR (#502) fails on tests related to Storybook. What's Node support looking like on your end?

[Sidnioulz]

@Sidnioulz Both my Node 22 upgrade PR (#511) and my Node 24 upgrade PR (#502) fails on tests related to Storybook. What's Node support looking like on your end?

We support 20.19+ or 22.12+ (and so, 24.0+). It's a bit difficult for me to figure out from CI output alone what's going on as your build process is different from ours. I'd examine what's in your Storybook dist folder, and what exactly it exports.

[Tobbe]

@Sidnioulz Do you happen to know what SB versions added support for the different Node versions? I'm still on SB 7. Wonder if that's why it's not working on Node 22 or 24

[Tobbe]

I noticed you still have an open issue for adding Node 24 support storybookjs/storybook#31434 (which is the reason I tried just going to Node 22 when I got stuck on the Node 24 upgrade PR)

Trying to figure out in what order I need to upgrade everything 😅

[Sidnioulz]

@Sidnioulz Do you happen to know what SB versions added support for the different Node versions? I'm still on SB 7. Wonder if that's why it's not working on Node 22 or 24

AH! Node 24 was some time during Storybook 9.1.x. I'm not too sure if Node 22 works with Storybook 7, we don't track that information as far as I know.

[Tobbe]

Node 24 was some time during Storybook 9.1.x.

Amazing! Makes me feel hopeful I'll be able to upgrade to Node 24!

So I'll try bumping our SB version to 8 and see if that unlocks Node 22 for us. If not I'll try SB 9 too, and in that case I'll probably jump straight to Node 24

[Tobbe]

Storybook v8 upgrade is merged #515
Storybook v9 upgrade is ongoing #517

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[Tobbe]

I did upgrade to SB v9, but then had to downgrade to v8 again due to storybookjs/storybook#33006
I'm guessing the Storybook team will prioritize other, more urgent, issues, so storybookjs/storybook#33006 will probably remain unresolved. Which means I'll never be able to upgrade to v9

The most likely path forward now is that I go straight to v10 (or 11 etc) once Cedar is fully ESM ready