You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hardcoding specific framework versions (e.g., "react": "18.2.0") in dependencies can create issues for consumers, such as dependency conflicts and reduced flexibility.
Problem Statement/Justification
For example, when I installed @pandacss/studio, which hardcodes react: 18.2.0, while my project uses react: 18.3.0, some of my packages were downgraded to match the hardcoded version. And as a result i have a bug during build:
You might have more than one copy of React in the same app
Proposed Solution or API
Use semantic version ranges or move shared frameworks like react, vite, etc., to peerDependencies with version ranges (e.g., "^18.0.0").
This discussion was converted from issue #2988 on November 19, 2024 19:52.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
Hardcoding specific framework versions (e.g.,
"react": "18.2.0"
) in dependencies can create issues for consumers, such as dependency conflicts and reduced flexibility.Problem Statement/Justification
For example, when I installed @pandacss/studio, which hardcodes
react: 18.2.0
, while my project usesreact: 18.3.0
, some of my packages were downgraded to match the hardcoded version. And as a result i have a bug during build:Proposed Solution or API
Use semantic version ranges or move shared frameworks like react, vite, etc., to peerDependencies with version ranges (e.g., "^18.0.0").
Beta Was this translation helpful? Give feedback.
All reactions