John Kane
John Kane
HHv3's intended switch to ESM will have knock on effects for HH's plugin system. We need to approach plugins, a key feature of the Hardhat ecosystem, carefully. We therefore want...
Create a document with a set of use cases of different complexity and of different kinds that reflect the need for multi-chain development flows as completely as possible. Potential use...
Create a document explaining: 1. The current features and use cases of the compilation pipeline 2. The limitations and issues with the current design 3. How remappings should work and...
Once EDR + HH has been released we want to fork `main` and create a proof of concept of HH that is ESM only. In particular we want to understand:...
There are many changes we would make to the HH compilation pipeline if we could make a breaking change. With HHv3 we have that opportunity. ## TODO - [ ]...
Sample most traces as before (1 in development, 0.001 in production), but exclude the `indexing` trace, which won't be sampled. Indexing happens once per session, and is being used to...
To better target our resources we want to understand which chains are seeing the most Ignition deploys. We need to capture that as part of our analytics. ## TODO -...
We put together a `hardhat-deploy` to Hardhat Ignition migration guide for our blog: https://blog.nomic.foundation/migrating-to-hardhat-ignition-from-hardhat-deploy-c17311bb658f We should add a version of it to our docs guide. I think we should add...
Ignition modules provide significant features (e.g. restartable deploys) but for the simplest case of deploying a single contract, it adds the boilerplate of declaring a module. Can we reduce/eliminate the...
We want to enhance our current set of guides, and add further guides to answer questions that keep coming up. ## TODO - [x] #598 - [ ] Using HH...