hashgraph / hashgraph/hedera-forking
Update the hardhat version to v3
- Dominant language
- Solidity
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
### Problem
Currently, if I were to setup a hardhat v3 project and tried installing `@hashgraph/system-contracts-forking`, I get error:
```
>> npm install --save-dev @hashgraph/system-contracts-forking
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: tutorial-hedera-fork-hardhat@1.0.0
npm error Found: hardhat@3.1.2
npm error node_modules/hardhat
npm error dev hardhat@"^3.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer hardhat@"^2.0.0" from @hashgraph/system-contracts-forking@0.1.2
npm error node_modules/@hashgraph/system-contracts-forking
npm error dev @hashgraph/system-contracts-forking@"^0.1.2" 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.
```
### Solution
Since Hardhat V3 is production ready and most users when setting up a new project end up using hardhat v3, I think it makes sense for us to support the plugin compatible with v3. Foundry works nicely.
### Alternatives
_No response_
Contributor guide
Research direction
No files or tests are named in the issue. Start by reproducing the npm installation conflict with hardhat@3 and inspecting the dependency configuration for @hashgraph/system-contracts-forking. The work is done when the package supports Hardhat v3 without the reported peer-dependency error and the existing checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100