reserve-protocol / protocol

Permissionless asset-backed, yield-bearing & overcollateralized stablecoins on Ethereum
Other
142 stars 103 forks source link

Build fails on ubuntu 22.04, node v16.16.0 #456

Closed AndreiD closed 1 year ago

AndreiD commented 1 year ago

Used on:

Linux me-desktop 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Node v16.16.0

Git clone this repo, npm install

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: reserve-protocol@1.0.0
npm ERR! Found: dotenv@10.0.0
npm ERR! node_modules/dotenv
npm ERR!   dev dotenv@"^10.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer dotenv@"^16.0.1" from @withtally/tally-publish-dao@0.0.5
npm ERR! node_modules/@withtally/tally-publish-dao
npm ERR!   dev @withtally/tally-publish-dao@"^0.0.5" 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/me/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/me/.npm/_logs/2022-11-07T10_36_55_322Z-debug-0.log

tried with yarn install

protocol git:(master) yarn install
 YN0000: ┌ Resolution step
 YN0002: │ reserve-protocol@workspace:. doesn't provide @ethersproject/abi (p537ba), requested by @typechain/ethers-v5
 YN0002: │ reserve-protocol@workspace:. doesn't provide @ethersproject/bytes (pcf58c), requested by @typechain/ethers-v5
 YN0002: │ reserve-protocol@workspace:. doesn't provide @ethersproject/providers (pe8ad9), requested by @typechain/ethers-v5
 YN0060: │ reserve-protocol@workspace:. provides dotenv (p30487) with version 10.0.0, which doesn't satisfy what @withtally/tally-publish-dao requests
 YN0060: │ reserve-protocol@workspace:. provides eslint (pfefd3) with version 8.19.0, which doesn't satisfy what eslint-config-standard requests
 YN0060: │ reserve-protocol@workspace:. provides eslint-plugin-promise (p68544) with version 6.0.0, which doesn't satisfy what eslint-config-standard requests
 YN0002: │ reserve-protocol@workspace:. doesn't provide lodash (pc563a), requested by @typechain/hardhat
 YN0002: │ reserve-protocol@workspace:. doesn't provide query-string (p64ac0), requested by @withtally/tally-publish-dao
 YN0060: │ reserve-protocol@workspace:. provides wretch (p082dd) with version 2.0.4, which doesn't satisfy what @withtally/tally-publish-dao requests
 YN0002: │ typechain@npm:3.0.0 doesn't provide typescript (p4ba7f), requested by ts-essentials
 YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
 YN0000: └ Completed
 YN0000: ┌ Fetch step
 YN0013: │ yargs@npm:16.2.0 can't be found in the cache and will be fetched from the remote registry
 YN0013: │ yargs@npm:17.5.1 can't be found in the cache and will be fetched from the remote registry
 YN0013: │ yargs@npm:4.8.1 can't be found in the cache and will be fetched from the remote registry
 YN0013: │ yn@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
 YN0013: │ yocto-queue@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
 YN0066: │ typescript@patch:typescript@npm%3A4.7.4#~builtin<compat/typescript>::version=4.7.4&hash=ddd1e8: Cannot apply hunk #2
 YN0018: │ ethereumjs-abi@https://github.com/ethereumjs/ethereumjs-abi.git#commit=ee3994657fa7a427238e6ba92a84d0b529bbcde0: The remote archive doesn't match the expected checksum
 YN0000: └ Completed in 20s 652ms
 YN0000: Failed with errors in 20s 774ms
AndreiD commented 1 year ago

fixed by updating dotenv to latest. should I do a push request or ...?

julianmrodri commented 1 year ago

@AndreiD Thanks for the info!. You can submit a PR, we wanted to review all our deps in depth, but if this is fixed by just dotenv we can probably proceed.

Make sure your branch it is up-to-date with master we pushed some yarn changes yesterday.

tbrent commented 1 year ago

Actually: @AndreiD if you could confirm master builds for you on ubuntu, I'll go ahead and close this issue. Thanks