allo-protocol / allo-v2

Core Allo V2 Contracts
GNU Affero General Public License v3.0
86 stars 65 forks source link

getting an upstream npm issue upon install #664

Closed owocki closed 15 hours ago

owocki commented 5 days ago
owocki@local /Users/owocki/Sites/allo-v2~ % npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @matterlabs/hardhat-zksync-deploy@0.1.5
npm error Found: ethers@6.13.2
npm error node_modules/ethers
npm error   dev ethers@"^6.7.1" from the root project
npm error   peer ethers@"*" from @ethereum-waffle/chai@4.0.10
npm error   node_modules/@ethereum-waffle/chai
npm error     @ethereum-waffle/chai@"4.0.10" from ethereum-waffle@4.0.10
npm error     node_modules/ethereum-waffle
npm error       dev ethereum-waffle@"^4.0.10" from the root project
npm error   11 more (@ethereum-waffle/compiler, @ethereum-waffle/ens, ...)
npm error
npm error Could not resolve dependency:
npm error peer ethers@"~5.5.4" from @matterlabs/hardhat-zksync-deploy@0.1.5
npm error node_modules/@matterlabs/hardhat-zksync-deploy
npm error   dev @matterlabs/hardhat-zksync-deploy@"^0.1.3" from the root project
npm error
npm error Conflicting peer dependency: ethers@5.5.4
npm error node_modules/ethers
npm error   peer ethers@"~5.5.4" from @matterlabs/hardhat-zksync-deploy@0.1.5
npm error   node_modules/@matterlabs/hardhat-zksync-deploy
npm error     dev @matterlabs/hardhat-zksync-deploy@"^0.1.3" 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 /Users/owocki/.npm/_logs/2024-09-13T19_40_40_599Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/owocki/.npm/_logs/2024-09-13T19_40_40_599Z-debug-0.log
linear[bot] commented 5 days ago

PAR-392 getting an upstream npm issue upon install

thelostone-mc commented 15 hours ago

Looks like this got resolved