Error: Couldn't find ethers-v5 (yarn workspaces)
See original GitHub issueI’m getting the following error on the latest version of typechain:
Error: Couldn't find ethers-v5. Tried loading: @typechain/ethers-v5, typechain-target-ethers-v5, /home/k/Projects/work/optimism/packages/contracts/ethers-v5.
Perhaps you forgot to install @typechain/ethers-v5?
This is happening within a yarn/lerna monorepo. It appears this is happening because the typechain
package is being hoisted to the root level, but the @typechain/ethers-v5
package is not.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Error: Couldn't find ethers-v5 · Issue #423 - GitHub
I am getting this error after trying to generate typechain files out of my artifacts: Error: Couldn't find ethers-v5.
Read more >@typechain/ethers-v5 - npm
@typechain/ethers-v5. TypeScript icon, indicating that this package has built-in type declarations. 10.2.0 • Public • Published 13 days ago.
Read more >yarn workspace not update the local package (making eslint ...
Problem. I'm making custom eslint plugin referencing working with plugins and generator-eslint. Then I make a monorepo using yarn workspace ...
Read more >@typechain/ethers-v5 | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >contract call: <unrecognizedcontract> - You.com | The AI ...
Error : missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Turns out it was just luck indeed. The issue randomly reappeared later even after upgrading to 7.0.0. After much trial and error, the only thing which fixed it for me was:
Just FYI, I’ve made target resolution more robust in the new version, so this should (no guarantees) be solved after the release.