-
-
Notifications
You must be signed in to change notification settings - Fork 0
Bench: storybook-1ad0785-0 #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: bench/storybook-1ad0785-0-base
Are you sure you want to change the base?
Bench: storybook-1ad0785-0 #12
Conversation
Greptile OverviewGreptile SummaryThis PR removes React and ReactDOM peer dependencies from multiple Storybook packages that don't actually require them at runtime. The changes affect 33 package.json files across framework packages (Angular, Vue, Ember, Web Components, etc.) and various addons. For framework packages, this corrects architectural inconsistencies where non-React frameworks were incorrectly requiring React dependencies. For addon packages, the changes involve restructuring dependencies by moving React from peerDependencies to devDependencies and relocating internal Storybook packages from runtime to development dependencies. This dependency cleanup makes packages more framework-agnostic, reduces unnecessary installation requirements, and aligns dependency declarations with actual runtime needs. Important Files Changed
Confidence score: 3/5
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
31 files reviewed, 2 comments
| "react": "^16.8.0", | ||
| "react-dom": "^16.8.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: Moving React from peerDependencies to devDependencies could cause runtime issues if consumers don't have React installed, since the addon likely needs React components at runtime. Are you certain this addon doesn't need React at runtime, or should React remain as a peer dependency?
Prompt To Fix With AI
This is a comment left during a code review.
Path: code/addons/storysource/package.json
Line: 70:71
Comment:
**logic:** Moving React from peerDependencies to devDependencies could cause runtime issues if consumers don't have React installed, since the addon likely needs React components at runtime. Are you certain this addon doesn't need React at runtime, or should React remain as a peer dependency?
How can I resolve this? If you propose a fix, please make it concise.| "react": "^16.8.0", | ||
| "react-dom": "^16.8.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logic: Moving React and React DOM from peerDependencies to devDependencies could cause issues. Since this is a React-specific addon, consumers typically expect React to be a peer dependency that they provide, not bundled with the addon. Will React be provided by the Storybook framework itself, or should this remain a peer dependency?
Prompt To Fix With AI
This is a comment left during a code review.
Path: code/addons/jest/package.json
Line: 85:86
Comment:
**logic:** Moving React and React DOM from peerDependencies to devDependencies could cause issues. Since this is a React-specific addon, consumers typically expect React to be a peer dependency that they provide, not bundled with the addon. Will React be provided by the Storybook framework itself, or should this remain a peer dependency?
How can I resolve this? If you propose a fix, please make it concise.
Recreation of PR: N/A
Benchmark PR
storybook-1ad0785-0.1ad0785220c3356cd2397290fbab934a2068194f91d4c5de87cba5f90d0f0baafae31af7e85beb79