-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better document how to set up a web3 instance #1609
Comments
Double-checking that its on your radar: I found the Providers docs surprisingly robust. I do think it could stand to be higher up in the table of contents, though, as its the first thing you'll need to configure before being able to use the lib. I wouldn't expect newcomers to guess that there's important setup information in the |
Yes, I agree, the |
👍 I'll make some tweaks and ping you for feedback. |
What was wrong?
There are many different ways to set up a web3 instance. For example:
But with each of these options comes certain configuration that needs to happen.
For example,
web3.auto
requires either an environment variable set, a local node running on mainnet, or an http provider running on localhost:8545. But you have to go to a different page in the docs to see that.Similarly, if you are trying to connect to a local geth node over HTTP or Websockets, you need to start geth with the
--rpc
or--ws
flag, respectively, in order to connect.It would be nice if the docs mentioned these nuances.
The text was updated successfully, but these errors were encountered: