Skip to content
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

Installing using expo and latest React Native throw error #78

Open
ecerichter opened this issue Dec 16, 2024 · 1 comment
Open

Installing using expo and latest React Native throw error #78

ecerichter opened this issue Dec 16, 2024 · 1 comment

Comments

@ecerichter
Copy link

Hi!
Trying to install using latest React Native throws the following exception:

PS C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI> npx expo install react-native-signature-pad
› Installing 1 other package using npm

npm install --save react-native-signature-pad
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error react@"18.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.4" from [email protected]
npm error node_modules/react-native-signature-pad
npm error react-native-signature-pad@"^0.1.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\richter\AppData\Local\npm-cache_logs\2024-12-16T13_19_08_311Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\richter\AppData\Local\npm-cache_logs\2024-12-16T13_19_08_311Z-debug-0.log
Error: npm install --save react-native-signature-pad exited with non-zero code: 1
Error: npm install --save react-native-signature-pad exited with non-zero code: 1
at ChildProcess.completionListener (C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI\node_modules@expo\spawn-async\build\spawnAsync.js:42:23)
at Object.onceWrapper (node:events:639:26)
at ChildProcess.emit (node:events:524:28)
at cp.emit (C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI\node_modules\cross-spawn\lib\enoent.js:34:29)
at maybeClose (node:internal/child_process:1101:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)
...
at spawnAsync (C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI\node_modules@expo\spawn-async\build\spawnAsync.js:7:23)
at NpmPackageManager.runAsync (C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI\node_modules@expo\package-manager\build\node\BasePackageManager.js:41:42)
at C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI\node_modules@expo\package-manager\build\node\NpmPackageManager.js:37:20
at C:\Users\richter\Documents\projects\AssinaturaRomaneio\AssinaturaRomaneioUI\node_modules@expo\package-manager\build\utils\spawn.js:19:34
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Result of npm ls:

PS C:\Users\richter\Documents\projects\MyApp\MyAppUI> npm ls
[email protected] C:\Users\richter\Documents\projects\MyApp\MyAppUI
├── @babel/[email protected]
├── @types/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Anything I'm missing? Can I help upgrade dependencies?

Thanks,

ER

@Jahanzeb009
Copy link

Jahanzeb009 commented Jan 1, 2025

try --force flag

npm i <library-name> --force

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants