-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Can't connect with Node.js #1051
Comments
Of course I figured it out after a minute of posting the issue: npm installs version 1.0 of web3, uninstalling it and installing v '0.20.2' resolved my problem. |
KenoLeon, Hi, how did you uninstall it and install the lower version? |
@albomo check: https://medium.com/@k3no/ethereum-tokens-smart-contracts-a263b43d4c54 Basically |
I see this is an older thread, but I wanted to ask -- the web3 documentation says that HttpProvider is deprecated, so I wonder if that's why it doesn't work with the newer versions of web3. It looks like this is only as related to subscriptions, so I guess its not that important if you're not using those? But I wonder if the proper approach is to use the newest version of web3 and use websockets instead? See the discussion of these different methods in the web3 documentation: https://web3js.readthedocs.io/en/1.0/web3.html |
I have parity running on one terminal with:
parity --chain kovan ui
Then on Atom I try to attach with:
When I run it with atom-runner or a node terminal I get undefined.
Running Parity/v1.6.10-stable,node 8.5.0/ web3 1.0.0-beta.20
The text was updated successfully, but these errors were encountered: