OS:
Platform:
SDK:
SDK version: 4.2.2
react-native version: 0.68.2
Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
I have following issue:
We use lodash.* do target exactly which module we need from lodash, but after buildeing our react-native-web app (which is also a react-native app), it appears looking at webpack-bundle-analyzer that one of our dependency (which is sentry-react-native) import the whole lodash. Is this necessary ?

see in red the multiple lodash we have now
Steps to reproduce:
- yarn add @sentry/react-native
- npm ls lodash
Actual result:
├─┬ @sentry/react-native@4.2.2
│ └─┬ @sentry/wizard@1.2.17
│ ├─┬ inquirer@6.5.2
│ │ └── lodash@4.17.21 deduped
│ └── lodash@4.17.21 deduped
Expected result:
├─┬ @sentry/react-native@4.2.2
│ └─┬ @sentry/wizard@1.2.17
│ ├─┬ inquirer@6.5.2
│ │ └── lodash.something@4.17.21
│ └── lodash.something@4.17.21
Related issues
OS:
Platform:
SDK:
@sentry/react-native(>= 1.0.0)react-native-sentry(<= 0.43.2)SDK version: 4.2.2
react-nativeversion: 0.68.2Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
I have following issue:
We use
lodash.*do target exactly which module we need fromlodash, but after buildeing our react-native-web app (which is also a react-native app), it appears looking at webpack-bundle-analyzer that one of ourdependency(which is sentry-react-native) import the whole lodash. Is this necessary ?see in red the multiple lodash we have now
Steps to reproduce:
Actual result:
Expected result:
Related issues