Merge pull request #184 from defi-wonderland/dev

chore: v2.3.5

docs/source/fakes.rst

@@ -11,7 +11,7 @@ When should I use a fake?
 -------------------------
 
 Fakes are a powerful tool when you want to test how a smart contract will interact with other contracts.
-Instead of initalizing a full-fledged smart contract to interact with, you can simply create a fake that can provide pre-programmed responses.
+Instead of initializing a full-fledged smart contract to interact with, you can simply create a fake that can provide pre-programmed responses.
 
 Fakes are especially useful when the contracts that you need to interact with are relatively complex.
 For example, imagine that you're testing a contract that needs to interact with another (very stateful) contract.

docs/source/getting-started.rst

@@ -78,3 +78,13 @@ If you'd like to use mocks, you **must** update your :code:`hardhat.config.<js/t
       }
 
       export default config
+
+Optional config to use Smock Matchers
+-------------------------------------
+
+
+  .. code-block:: typescript
+    // ContractTest.ts
+      
+    import { smock } from '@defi-wonderland/smock';
+    chai.use(smock.matchers);

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@defi-wonderland/smock",
-  "version": "2.3.4",
+  "version": "2.3.5",
   "description": "The Solidity mocking library",
   "keywords": [
     "ethereum",

src/utils/hardhat.ts

@@ -29,6 +29,14 @@ export const getHardhatBaseProvider = async (runtime: HardhatRuntimeEnvironment)
   // Search by looking for the internal "_wrapped" variable. Base provider doesn't have this
   // property (at least for now!).
   let provider: any = runtime.network.provider;
+
+  if ('init' in provider) {
+    // Newer versions of Hardhat initialize the provider lazily, so we need to
+    // call provider.init() explicitly. This is a no-op if the provider is
+    // already initialized.
+    await provider.init();
+  }
+
   while (provider._wrapped !== undefined) {
     provider = provider._wrapped;