You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -445,8 +445,8 @@ Please add the property "type" with the value "module" in your package.json to e
445
445
CONFIG_VARIABLE_FORMAT_MUST_INCLUDE_VARIABLE: {
446
446
number: 19,
447
447
messageTemplate: `The format string "{format}" must include {marker} marker`,
448
-
websiteTitle: "Config variable format must include {variable}",
449
-
websiteDescription: `The config variable format must include the string "{variable}", which will be replaced with the actual value of the variable.`,
448
+
websiteTitle: "Config variable format must include \\{variable\\}",
449
+
websiteDescription: `The config variable format must include the string "\\{variable\\}", which will be replaced with the actual value of the variable.`,
450
450
},
451
451
INVALID_FULLY_QUALIFIED_NAME: {
452
452
number: 20,
@@ -1118,7 +1118,7 @@ Please check Hardhat's output for more details.`,
1118
1118
number: 911,
1119
1119
messageTemplate: `A wasm version of solc {version} is invalid. The compile function is not available.`,
1120
1120
websiteTitle: "Invalid solcjs compiler",
1121
-
websiteDescription: `Hardhat successfully downloaded a WASM version of solc {version} but it is invalid. The compile function is missing.`,
1121
+
websiteDescription: `Hardhat successfully downloaded a WASM version of solc but it is invalid. The compile function is missing.`,
1122
1122
},
1123
1123
BUILD_PROFILE_NOT_FOUND: {
1124
1124
number: 912,
@@ -1977,11 +1977,13 @@ Please try again later.`,
1977
1977
websiteTitle: "Network not found",
1978
1978
websiteDescription: `No network with the specified chain id was found. You can override the chain by passing it as a parameter to the client getter:
1979
1979
1980
+
\`\`\`ts
1980
1981
import { someChain } from "viem/chains";
1981
1982
const client = await hre.viem.getPublicClient({
1982
1983
chain: someChain,
1983
1984
...
1984
1985
});
1986
+
\`\`\`
1985
1987
1986
1988
You can find a list of supported networks here: https://github.com/wevm/viem/blob/main/src/chains/index.ts`,
1987
1989
},
@@ -2002,12 +2004,15 @@ Please ensure you're using one of the supported networks.`,
2002
2004
2003
2005
To resolve this, make sure to add an account to the specified network in the Hardhat config. Alternatively, you can set a custom wallet client by passing it as a parameter in the relevant function:
@@ -2237,9 +2242,9 @@ This might be caused by using hardhat_reset and loadFixture calls in a testcase.
2237
2242
messageTemplate:
2238
2243
"The .revertedWithCustomError matcher expects two arguments: the contract and the custom error name. Arguments should be asserted with the .withArgs helper.",
2239
2244
websiteTitle:
2240
-
"Invalid arguments length for the .revertedWithCustomError matcher",
2245
+
"Invalid arguments length for the .revertedWithCustomError matcher",
2241
2246
websiteDescription:
2242
-
"Invalid arguments length for the .revertedWithCustomError matcher",
2247
+
"Invalid arguments length for the .revertedWithCustomError matcher",
2243
2248
},
2244
2249
WITH_ARGS_FORBIDDEN: {
2245
2250
number: 70011,
@@ -2345,7 +2350,9 @@ This might be caused by using hardhat_reset and loadFixture calls in a testcase.
2345
2350
websiteTitle: "Network not supported",
2346
2351
websiteDescription: `The network is not supported by hardhat-verify. To see the list of supported networks, run:
2347
2352
2348
-
npx hardhat verify --list-networks
2353
+
\`\`\`sh
2354
+
npx hardhat verify --list-networks
2355
+
\`\`\`
2349
2356
2350
2357
To add support for a new network, see https://hardhat.org/verify-custom-networks`,
2351
2358
},
@@ -2354,17 +2361,19 @@ To add support for a new network, see https://hardhat.org/verify-custom-networks
2354
2361
messageTemplate: `The request to {url} failed with the message "{errorMessage}". This error comes from {name}, not Hardhat.`,
2355
2362
websiteTitle: "Explorer request failed",
2356
2363
websiteDescription: `The request to the explorer failed.
2364
+
2357
2365
- Verify that the URL is correct.
2358
-
- Ensure the {name} service is up and reachable.
2366
+
- Ensure the service is up and reachable.
2359
2367
- Check your network connection and try again.`,
2360
2368
},
2361
2369
EXPLORER_REQUEST_STATUS_CODE_ERROR: {
2362
2370
number: 80002,
2363
2371
messageTemplate: `The request to {url} returned a non-success status code {statusCode}: "{errorMessage}". (This response comes from {name}, not Hardhat.)`,
2364
2372
websiteTitle: "Explorer request status code error",
2365
2373
websiteDescription: `The request to the explorer returned a non-success status code.
2374
+
2366
2375
- Verify that the URL is correct.
2367
-
- Ensure the {name} service is up and reachable.
2376
+
- Ensure the service is up and reachable.
2368
2377
- Check your network connection and try again.`,
2369
2378
},
2370
2379
SOLC_VERSION_NOT_SUPPORTED: {
@@ -2388,6 +2397,7 @@ Please verify the address and selected network, and try again.`,
2388
2397
websiteDescription: `The Solidity compiler version used to compile the deployed contract does not match any of the versions configured in your Hardhat project.
2389
2398
2390
2399
This mismatch may indicate:
2400
+
2391
2401
- You're not on the same commit that was used to deploy the contract.
2392
2402
- The compiler version in your Hardhat config is incorrect.
2393
2403
- The address provided is not the deployed contract.
@@ -2411,6 +2421,7 @@ This mismatch may indicate:
2411
2421
websiteTitle: "Build info compiler version mismatch",
2412
2422
websiteDescription: `The compiler version in the build info does not match the version encoded in the deployed bytecode.
2413
2423
Possible causes:
2424
+
2414
2425
- Compiler settings were changed after deployment.
2415
2426
- The contract address is incorrect.
2416
2427
- The selected network is incorrect.`,
@@ -2422,7 +2433,8 @@ Possible causes:
2422
2433
websiteDescription: `The bytecode at the specified address did not match the expected contract.
2423
2434
2424
2435
Possible causes:
2425
-
- Your artifacts are outdated or missing; try running npx hardhat compile --force --buildProfile production.
2436
+
2437
+
- Your artifacts are outdated or missing; try running \`npx hardhat compile --force --buildProfile production\`.
2426
2438
- The contract code was modified after deployment.
2427
2439
- Compiler settings (optimizer, EVM version, etc.) changed after deployment.
2428
2440
- The provided address is incorrect.
@@ -2433,11 +2445,14 @@ Possible causes:
2433
2445
messageTemplate: `More than one contract matches the deployed bytecode:
2434
2446
{fqnList}
2435
2447
2436
-
Specify the exact contract using the "--contract" flag.`,
2448
+
Specify the exact contract using the \`--contract\` flag.`,
2437
2449
websiteTitle: "Multiple contract matches",
2438
-
websiteDescription: `The deployed bytecode matches multiple compiled contracts. Specify the exact contract using the "--contract" flag. For example:
If the contract uses external libraries, verify that the provided name matches the fully qualified name (FQN) of one of them, such as:
2457
2472
2458
-
contracts/Math.sol:SafeMath`,
2473
+
\`\`\`
2474
+
contracts/Math.sol:SafeMath
2475
+
\`\`\`
2476
+
`,
2459
2477
},
2460
2478
LIBRARY_MULTIPLE_MATCHES: {
2461
2479
number: 80013,
@@ -2469,15 +2487,18 @@ To fix this, specify one of these fully qualified library names and try again.`,
2469
2487
2470
2488
To resolve the ambiguity, provide the fully qualified library name in the format:
2471
2489
2472
-
path/to/LibraryFile.sol:LibraryName`,
2490
+
\`\`\`
2491
+
path/to/LibraryFile.sol:LibraryName
2492
+
\`\`\`
2493
+
`,
2473
2494
},
2474
2495
DUPLICATED_LIBRARY: {
2475
2496
number: 80014,
2476
2497
messageTemplate: `The library name "{library}" and its fully qualified name "{libraryFqn}" refer to the same library.
2477
2498
2478
2499
To fix this, remove one of them and try again.`,
2479
2500
websiteTitle: "Duplicated library entry",
2480
-
websiteDescription: `The same library was specified more than once using both its short name and fully qualified name (FQN) in the "--libraries" option.
2501
+
websiteDescription: `The same library was specified more than once using both its short name and fully qualified name (FQN) in the \`--libraries\` option.
2481
2502
2482
2503
Only one form should be used for each library. Remove one of the entries and try again.`,
2483
2504
},
@@ -2601,6 +2622,7 @@ Block explorer information is missing in your chain descriptor configuration.
2601
2622
To enable contract verification, add an entry for the verification provider in the blockExplorers field of the relevant chain descriptor.
2602
2623
You can override the default chain descriptor by providing your own chainDescriptors object in the Hardhat config, with the following structure:
2603
2624
2625
+
\`\`\`
2604
2626
chainDescriptors: {
2605
2627
<chainId>: {
2606
2628
name: <name>,
@@ -2610,7 +2632,7 @@ chainDescriptors: {
2610
2632
}
2611
2633
}
2612
2634
}
2613
-
2635
+
\`\`\`
2614
2636
`,
2615
2637
},
2616
2638
ADDRESS_NOT_A_CONTRACT: {
@@ -2625,6 +2647,7 @@ Please verify the address and network, and try again later if necessary.`,
2625
2647
messageTemplate: `The {verificationProvider} API key is empty.`,
2626
2648
websiteTitle: "Block explorer API key is empty",
2627
2649
websiteDescription: `The provided API key for the block explorer is empty. This can happen in the following cases:
2650
+
2628
2651
- No "apiKey" field is configured in the hardhat config.
2629
2652
- The "apiKey" is explicitly set to an empty string in the Hardhat config.
2630
2653
- The "apiKey" is assigned to a config variable that resolves to an empty string at runtime.
@@ -2655,7 +2678,10 @@ To resolve this, set a valid non-empty API key in your Hardhat config, then try
0 commit comments