Public Ticket #2984

Installation Issue

Open
Comments
DexignLab
Yamini Gaur replied 1 week ago on June 27, 2022 at 12:56 PM

Hello William O'Hara,

Okay!! you can change or remove dependencies as you want.

Thanks

DexignLab
William O'Hara replied 1 week ago on June 24, 2022 at 04:10 PM

yes I do, but  I have been going the route of removing some dependencies. I am not sure i understand peer dependencies well though - but i will use this as a way to get an understanding of it. 

DexignLab 1
Yamini Gaur replied 1 week ago on June 24, 2022 at 05:21 AM

Hello William O'Hara,

Thanks for being our customer.

Sorry for the late reply. 

Please use node version 12 -13 or if you want to use the latest package then remove some dependencies like @metismenu/[email protected]"0.0.2", etc because this is based on the old version.

I hope now you understand how to use the package according to the node version.

Thanks & Regards

Yamini

DexignZone

DexignLab
William O'Hara replied started the conversation 2 weeks ago on June 22, 2022 at 09:26 PM

there is a dependency issue when i try to install using npm ...

$ npm i

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! [email protected]"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer [email protected]"^16.13.1" from @metismenu/[email protected]
npm ERR! node_modules/@metismenu/react
npm ERR! @metismenu/[email protected]"0.0.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/williamohara/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/williamohara/.npm/_logs/2022-06-22T20_58_10_685Z-debug-0.log

I tried running with --force parameter, but it still will give me too many critical vulnerabilities "npm audit fix" will not fix it. how do i deal with this dependency - anyone?