delay VS hardhat

Manually creating a Promise can look challenging, but you don't have to do that if you stick to async/await and Promise-based APIs. For example, you can use the npm package delay for a promisified version of setTimeout.

`git log --graph --decorate --oneline` is specific to a branch of a repository. Github Network shows the relationship between forks. It is similar but really the question answered by it is "what and where is the work being done" and "what is the relationship between work being done and this repository I'm looking at". It sucks that Network is buried, I think it should be much more accessible.

Eg https://github.com/sindresorhus/delay/network tells me that this work is being maintained actively, but most forks are not merging back. Another one might tell me work on the main fork is stalled, and many users are now doing PRs against a fork of the original.

To make sure last action is ended before doing another one, I add some delay between actions using delay.

For a list of all the built-in tasks and subtasks please take a look at task-names.ts

Let’s now get the account’s balance. The Hardhat Runtime Environment will be available in the global scope. By using Hardhat’s ether.js plugin, which is included in the Hardhat Toolbox, we get access to an ethers.js instance:

Plugins can extend the HRE. For example, hardhat-ethers adds a Ethers.js instance to it, making it available to tasks, tests and scripts.