-
Notifications
You must be signed in to change notification settings - Fork 679
fix: make forking work in the browser #3130
Conversation
02abbfe
to
18fc14a
Compare
You can test this by checking out this branch and then running: $ npm run reinstall && INFURA_KEY=<YOUR INFURA KEY HERE> npm run build && npm run docs.build && npm run docs.preview then paste the following in any of the editors: const p = ganache.provider({fork:"mainnet"});
console.log(await p.request({method:"debug_traceTransaction", params:["0x560900937892cd888a685c836f666804e05e04f3d161e1751ffb5ab7809c55d9"]})); then wait a while for the result to appear (it can takes a lot of time). Additionally, you should test the http handler code (the above tests WebSockets): const p = ganache.provider({fork:{url: "<your infura url goes here>"}});
console.log(await p.request({method:"debug_traceTransaction", params:["0x560900937892cd888a685c836f666804e05e04f3d161e1751ffb5ab7809c55d9"]})); Example: |
6f8cce3
to
7cf328f
Compare
4831915
to
290f894
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢 it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Soooo cooooooool! All it needs is a release-ready PR description!
I've also pushed two changes to the README to this branch if you could review them. Let me know and I can remove this commits from your branch, I just knew you were out of town and thought it would be easier to push than have you go in and update the README.
638c72c
to
8c5aac3
Compare
blocked by #3275 |
There are no changes to address but GitHub demands I address them.
8c5aac3
to
8c2ae9b
Compare
Ganache's zero-config forking feature now works in the browser!