-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Ignition viem to use viem 2 #692
Labels
status:ready
This issue is ready to be worked on
Comments
@zoeyTM the HH-viem update is in this branch, though not yet released: NomicFoundation/hardhat#4875 |
kanej
pushed a commit
that referenced
this issue
Feb 21, 2024
Update `hardhat-ignition-viem` to use `viem@2`, this requires updating the version of `hardhat-viem` used to `2.0.0` to get its `viem@2` version. Resolves #692
kanej
pushed a commit
that referenced
this issue
Feb 21, 2024
Update `hardhat-ignition-viem` to use `viem@2`, this requires updating the version of `hardhat-viem` used to `2.0.0` to get its `viem@2` version. Resolves #692
kanej
pushed a commit
that referenced
this issue
Feb 21, 2024
Update `hardhat-ignition-viem` to use `viem@2`, this requires updating the version of `hardhat-viem` used to `2.0.0` to get its `viem@2` version. Resolves #692
kanej
pushed a commit
that referenced
this issue
Feb 21, 2024
Update `hardhat-ignition-viem` to use `viem@2`, this requires updating the version of `hardhat-viem` used to `2.0.0` to get its `viem@2` version. Resolves #692
Merged
kanej
pushed a commit
that referenced
this issue
Feb 21, 2024
Update `hardhat-ignition-viem` to use `viem@2`, this requires updating the version of `hardhat-viem` used to `2.0.0` to get its `viem@2` version. Resolves #692
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This change is happening in
hardhat-viem
and will roll out into the toolbox. To avoid a conflict when Ignition is included in the toolbox we should update to latest versions ofviem
andhardhat-viem
.The text was updated successfully, but these errors were encountered: