Describe the bug
"expo" is listed as a dependency in the core project but only used in the Example project. Is there a reason for this? It is causing warnings to be thrown in non-expo projects due to a missing peer dependency. Maybe it needs to move to devDependencies?
To Reproduce
In a non-expo project, add "@react-native-seoul/masonry-list": "1.4.2", to package.json and run yarn install, see warning:
YN0002: │ @test/mobile@workspace:packages/mobile doesn't provide expo (pb91be), requested by @react-native-seoul/masonry-list
Expected behavior
No warnings should print to console unless expo is being used in the core project itself. Maybe we need
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
using Yarn 3 and it shows warnings to help manage peer deps
Describe the bug "expo" is listed as a dependency in the core project but only used in the Example project. Is there a reason for this? It is causing warnings to be thrown in non-expo projects due to a missing peer dependency. Maybe it needs to move to
devDependencies?To Reproduce In a non-expo project, add
"@react-native-seoul/masonry-list": "1.4.2",topackage.jsonand runyarn install, see warning:Expected behavior No warnings should print to console unless expo is being used in the core project itself. Maybe we need
Screenshots N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context using Yarn 3 and it shows warnings to help manage peer deps