JsonRpcProvider returns empty response

[NickStein85]

Ethers Version

6.8.0

Search Terms

No response

Describe the Problem

I want to create tests and check if provider contains _isProvider true but getting an empty response.

Code Snippet

const { ethers } = require("ethers");

const provider = new ethers.JsonRpcProvider("https://eth.llamarpc.com");

console.log(provider);

Contract ABI

No response

Errors

No response

Environment

No response

Environment (Other)

No response

[ricmoo]

The result isn’t empty. It depends on your environment and its implementation of console.log.

So, any of the values defined by getters are present, but they are not enumerated by console.log (in node.js; generally the interactive log in a web browser is far more attentive).

This is because a getter can have side-effects, and no one wants console.log to mutate the state of an object.

I also believe, _isProvider is no longer a property in v6. Instead, the focus is on capability-checking; e.g. if an object has a estimateGas function then it will be used during ContractRunner. As a result method signatures have been adjusted to make sure the arguments and return types are shared across possible objects that can be passed in (such as Provider now uses broadcast transaction, since the sendTransaction of Providers and Signers in v5 were incompatible).

Make sense?

[NickStein85]

Perfect! Thank you for the response. Changed to this and it worked:

const { ethers } = require("ethers");

const provider = new ethers.JsonRpcProvider("https://eth.llamarpc.com");

provider.getBlockNumber()
    .then(blockNumber => {
        console.log(`Connected successfully. Current block number is ${blockNumber}`);
    })
    .catch(error => {
        console.error('Error connecting to provider:', error);
    });

[kypanz]

This is intersting, my English is not the best but i am curious of why this happend

• where i can learn how some properties cant be enumerated in nodejs but in web browser yes ?
• have a specific name for this situation ?

I wanna learn more about this, to solved in my lastets proyect i downgrade the version of ethers to the ethers@5.7.2 to use the ethers.providers propertie and in that version i can use console.log, but this is intersting because works in ethers 6.8.1 but i cant see the logs, is a little tricky for me to understand if i am connected fine or not

• where i can learn more about this cases in deep ? to understand why in nodejs this happend
• there exist a function in the new verison of ethers to see if i am connected fine ? or i need to use the getBlockNumber function every time when i need to check the connection ?

Thanks for read, have a nice week ❤️