Currently, the Select component in Gluestack V5 relies on @legendapp/motion for its animations. However, it seems that @legendapp/motion is not actively maintained. Its outdated peer dependencies cause conflicts with newer versions of React and React Native, forcing developers to use the --legacy-peer-deps flag during installation.
Why is this a problem?
Requiring --legacy-peer-deps disrupts the standard npm install workflow and can lead to an unstable dependency tree across the entire project. It makes project maintenance difficult and degrades the developer experience.
I'd love to hear your thoughts on the best approach for the project.
Currently, the
Selectcomponent in Gluestack V5 relies on@legendapp/motionfor its animations. However, it seems that@legendapp/motionis not actively maintained. Its outdated peer dependencies cause conflicts with newer versions of React and React Native, forcing developers to use the--legacy-peer-depsflag during installation.Why is this a problem?
Requiring
--legacy-peer-depsdisrupts the standardnpm installworkflow and can lead to an unstable dependency tree across the entire project. It makes project maintenance difficult and degrades the developer experience.I'd love to hear your thoughts on the best approach for the project.