These are just a few simple logging utilities provided to simplify and standardize the error facilities across the Ethers library.
The Logger library has zero dependencies and is intentionally very light so it can be easily included in each library.
The Censorship functionality relies on one instance of the Ethers library being included. In large bundled packages or when npm link is used, this may not be the case. If you require this functionality, ensure that your bundling is configured properly.
Logger
Create a new logger which will include version in all errors thrown.
Log debugging information.
Log generic information.
Log warnings.
These functions honor the current Censorship and help create a standard error model for detecting and processing errors within Ethers.
Create an Error object with message and an optional code and additional params set. This is useful when an error is needed to be rejected instead of thrown.
Throw an Error with message and an optional code and additional params set.
Throw an INVALID_ARGUMENT Error with name and value.
There can be used to ensure various properties and actions are safe.
Checks that target is not kind and performs the same operatons as checkNew. This is useful for ensuring abstract classes are not being instantiated.
If count is not equal to expectedCount, throws a MISSING_ARGUMENT or UNEXPECTED_ARGUMENT error.
If target is not a valid this or target value, throw a MISSING_NEW error. This is useful to ensure callers of a Class are using new.
Check that the environment has a correctly functioning String.normalize. If not, a UNSUPPORTED_OPERATION error is thrown.
If value is not safe as a JavaScript number, throws a NUMERIC_FAULT error.
Set error censorship, optionally preventing errors from being uncensored.
In production applications, this prevents any error from leaking information by masking the message and values of errors.
This can impact debugging, making it substantially more difficult.
Set the log level, to suppress logging output below a particular log level.
Every error in Ethers has a code value, which is a string that will match one of the following error codes.
The operation is not implemented.
There was an error communicating with a server.
The amount of data needed is more than the amount of data required, which would cause the data buffer to read past its end.
There was an invalid operation done on numeric values.
Common cases of this occur when there is overflow, arithmetic underflow in fixed numeric types or division by zero.
The type or value of an argument is invalid. This will generally also include the name and value of the argument. Any function which accepts sensitive data (such as a private key) will include the string [[REDACTED]] instead of the value passed in.
An attempt to call a blockchain contract (getter) resulted in a revert or other error.
The account is attempting to make a transaction which costs more than is available.
A sending account must have enough ether to pay for the value, the gas limit (at the gas price) as well as the intrinsic cost of data. The intrinsic cost of data is 4 gas for each zero byte and 68 gas for each non-zero byte.
An Ethereum network validation error, such as an invalid chain ID.
The nonce being specified has already been used in a mined transaction.
When replacing a transaction, by using a nonce which has already been sent to the network, but which has not been mined yet the new transaction must specify a higher gas price.
This error occurs when the gas price is insufficient to bribe the transaction pool to prefer the new transaction over the old one. Generally, the new gas price should be about 50% + 1 wei more, so if a gas price of 10 gwei was used, the replacement should be 15.000000001 gwei.
When estimating the required amount of gas for a transaction, a node is queried for its best guess.
If a node is unable (or unwilling) to predict the cost, this error occurs.
The best remedy for this situation is to specify a gas limit in the transaction manually.
This error can also indicate that the transaction is expected to fail regardless, if for example an account with no tokens is attempting to send a token.
Log all output, including debugging information.
Only log output for infomational, warnings and errors.
Only log output for warnings and errors.
Only log output for errors.
Do not output any logs.