Repository navigation
Docs: Document experimentalDocgenServer feature flag - #35326
Merged
Merged
Conversation
Add API reference, config snippets, and cross-links so users can opt into server-side React docgen and understand how it relates to manifests and code examples. Co-authored-by: Cursor <cursoragent@cursor.com>
JReinhold
commented
Jun 30, 2026
kylegach
marked this pull request as ready for review
June 30, 2026 21:08
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR adds documentation for a new ChangesexperimentalDocgenServer documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Comment |
kylegach
approved these changes
Jun 30, 2026
2 tasks done
2 of 9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #
What I did
Document the
experimentalDocgenServerfeature flag in the main config features API reference.featurestype block and a new section covering server-side docgen, static snippets, manifest/MCP benefits, and tradeoffsmain-config-features-experimental-docgen-server.md) for CSF 3 and CSF NextcomponentsManifest,experimentalCodeExamples, and the manifests guideChecklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
Caution
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
?renderer=react).experimentalDocgenServersection appears beforeexperimentalCodeExamples, with the Experimental badge, defaultfalse, and a working code snippet.componentsManifestsection mentions the ref-based manifest format when combined with docgen server.experimentalCodeExamplesrecommendsexperimentalDocgenServerinstead.discussions/TODO) for a follow-up once the GitHub Discussion is opened.Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsDeclare whether manual QA will be needed for this PR during the next release, through
qa:neededorqa:skipMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>Made with Cursor
Summary by CodeRabbit