Cleanup: Package descriptions and keywords#32284
Merged
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit 8b34b0a
☁️ Nx Cloud last updated this comment at |
704e3a6 to
687fd5d
Compare
Contributor
There was a problem hiding this comment.
@shilman, I have a quick question about one item. The "Docs" addon (and probably others) still have the "essentials" keyword, and I was wondering if you'd be okay with removing it, as the "Essentials" addon is now technically part of core. Let me know, and we'll go from there.
Member
Author
There was a problem hiding this comment.
I didn't remove that since I think it's still used by the addon catalog somehow
jonniebigodes
approved these changes
Aug 18, 2025
Contributor
jonniebigodes
left a comment
There was a problem hiding this comment.
@shilman took a pass at this and left some items for you to look into when you can; nothing is blocking.
3646021 to
8b34b0a
Compare
This was referenced Aug 19, 2025
Merged
ndelangen
pushed a commit
that referenced
this pull request
Aug 20, 2025
Documentation: Clean up package descriptions and keywords (cherry picked from commit a24b910)
ndelangen
pushed a commit
that referenced
this pull request
Aug 20, 2025
Documentation: Clean up package descriptions and keywords (cherry picked from commit a24b910)
ndelangen
pushed a commit
that referenced
this pull request
Aug 21, 2025
Documentation: Clean up package descriptions and keywords (cherry picked from commit a24b910)
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 N/A
What I did
Clean up package descriptions & keywords across all packages in the monorepo
🦋 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 canary-release-pr.yml --field pr=<PR_NUMBER>Greptile Summary
This PR systematically cleans up package metadata across 33 packages in the Storybook monorepo by standardizing descriptions and expanding keywords for better npm discoverability. The changes establish consistent patterns:
Description standardization: Most packages now follow the format "Storybook [Package Type]: [Action/Purpose]" (e.g., "Storybook CLI: Develop, document, and test UI components in isolation"). Framework packages use "Storybook for [Framework]: Develop, document, and test UI components in isolation" while addons use "Storybook [Addon Name]: [Specific functionality]".
Keyword expansion: Keywords are expanded from minimal sets (often just "storybook") to comprehensive arrays that include:
storybook-framework,storybook-addon,storybook-renderer,storybook-builder)component,components,cli,test)The changes affect core packages (CLI tools, builders, renderers), framework integrations (React, Vue, Angular, Svelte, Next.js, etc.), and addons (a11y, docs, themes, etc.). All modifications are purely metadata improvements - no functional code, dependencies, or exports are changed, maintaining backward compatibility while improving package discoverability in npm searches.
Confidence score: 5/5