yarn install doesn't work out of the box
davidawad opened this issue · comments
fresh clone
david@sodium ~/P/W/c/solidity-template> node --version 1 main-?
v16.14.0
david@sodium ~/P/W/c/solidity-template> yarn install main-?
➤ YN0000: ┌ Resolution step
➤ YN0002: │ @codechecks/client@npm:0.1.12 doesn't provide typescript (pb3185), requested by ts-node
➤ 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 in 1s 54ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ ethereumjs-abi@https://github.com/ethereumjs/ethereumjs-abi.git#commit=1a27c59c15ab1e95ee8e5c4ed6ad814c49cc439e can't be found in the cache and will be
➤ YN0013: │ ethereumjs-abi@git+https://github.com/ethereumjs/ethereumjs-abi.git#commit=1a27c59c15ab1e95ee8e5c4ed6ad814c49cc439e can't be found in the cache and will
➤ YN0018: │ ethereumjs-abi@git+https://github.com/ethereumjs/ethereumjs-abi.git#commit=1a27c59c15ab1e95ee8e5c4ed6ad814c49cc439e: The remote archive doesn't match the expected checksum
➤ YN0000: └ Completed in 2s 181ms
➤ YN0000: Failed with errors in 3s 240ms
I was able to resolve this by disabling nvm and using yarn from a fresh brew install yarn along with the latest version of node 17.6.0
Feel free to remove this issue if it's stupid @paul, thank you for the wonderful template.
Hi @davidawad, unfortunately I couldn't replicate this issue. I just pulled a local copy of the template and it worked like a charm. I'm on node v16.13.0 and yarn v1.22.17 installed via npm.
When a yarn install command fails there's a near infinite number of possible causes. Unless it's something that keeps on happening to a large number of users, it's probably related to your local yarn installation.
At any rate, I'm glad that you managed to solve it eventually. FWIW I recommend using fnm for installing Node.js - it's the fastest node version manager out there.
no problem, I totally understand @PaulRBerg.
I was able to build exactly what I needed with this so I'm more than thankful for the tooling.
~ cheers 🍻
I am able to replicate this issue using yarn workspaces. The workspace has 5 packages, each has its own installation of this repo with git/commit related dependencies removed.
matthew@Matthews-MacBook-Pro shipyard % yarn
➤ YN0000: ┌ Resolution step
➤ 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 in 0s 441ms
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 567ms
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0000: └ Completed in 0s 220ms
➤ YN0000: Done with warnings in 1s 460ms
matthew@Matthews-MacBook-Pro shipyard % node -v
v16.14.2
matthew@Matthews-MacBook-Pro shipyard % yarn -v
3.2.0Hi @matabeitt, in your logs it says "Done with warnings", which means the installation worked. What am I missing?
@PaulRBerg this must have been an ID-10T error on my part.