Richard Moore comments

Results 530 comments of


                                            Richard Moore

Cannot be bundled for target `node` with webpack

The problem with relying on `"browser"` is that it doesn’t get pulled in by default in environments where it is difficult to specify `"mainFields"`. I tried this method originally and...

Cannot be bundled for target `node` with webpack

Looks like it is deprecated: https://gist.github.com/etaletai13/c1c3f47ec89459dfb3e049975115165c#jsnextmain

Cannot be bundled for target `node` with webpack

It was the top link in DuckDuckGo. I’m just trying to find info on these alternate properties...

Cannot be bundled for target `node` with webpack

See: https://webpack.js.org/configuration/resolve/#resolvemainfields But set the `mainFields` to `[ "main" ]`.

Only fire events that were triggered at future blocks

I’m still catching up on issues and preparing a minor bump. Is this problem occurring on an Ethereum network? Or is is another network, like BSC or matic? I worry...

Only fire events that were triggered at future blocks

I am wondering if this is a bug in hardhat? So, you are saying you subscribe to an event on a Hardhat in-memory node, and you get old events? When...

Only fire events that were triggered at future blocks

It shouldn’t send a request with a from block of -2, if it is, that is a bug. The -2 is a sentinel value only used for indicating it hasn’t...

Only fire events that were triggered at future blocks

Ok. I’ll look into that. That would be a bug.

Only fire events that were triggered at future blocks

Don’t worry about that too much yet. I’ll add some console.log statements to the code so I can see things and add more context.

Only fire events that were triggered at future blocks

@hickscorp The `.on` and `.once` set up a listener for events and will ignore `fromBlock` and `toBlock`. If you want to use getLogs you should either use the `provider.getLogs` or...