microsoft / microsoft/fluentui
Storybook 11 Support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20.3k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 46
Description
Storybook 11 Support
Hi there! 👋
The Storybook team is excited to announce that Storybook 11.0.0 is coming soon!
What's changing?
The key changes that affect addon authors are:
- CSF Next becomes default
- Many deprecated APIs are removed
- The
TABaddon type is removed
What do you need to do?
- Review the addon migration guide
- Adjust your repository following the guide's recommendations
- Test your addon with the prerelease version:
npm install --save-dev storybook@next
[!TIP]
The addon migration guide contains an AI prompt to help you migrate!
Need help?
- Join the
#addonschannel 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 11. If you have any feedback about this process or would like to opt-out from future outreach, please let us know on Discord.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Storybook 11 addon migration guide, then inspect this repository's Storybook configuration and addon usage for CSF Next, deprecated APIs, and the removed TAB addon type. Install the prerelease with npm install --save-dev storybook@next, test the addon, and consider the work done when it supports Storybook 11 without migration-related issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, storybook, typescript
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100