acolytec3
acolytec3
Correct. I need to figure out how to cleanly update the types for `asyncEventEmitter`. The hacks described in this thread all work in some sense but I haven't been able...
I ran the VM benchmarks with the new `eventemitter2` dependency and below are the results vs current master (basically identical). ``` eventemitter2 Number of blocks to sample: 10 Block 9422905...
Can we close this now that we have the meta issue #2375 and the PR branch?
In looking at these, the first two look to be easily addressable. Looks like the only difference would be that we would do `import * as AsyncEventEmitter from 'async-eventemitter'` since...
@thevaizman Could you try building your app and point your EVM dependency to the head of #2303 and see if that resolves your issue? Updating these import/exports doesn't seem to...
Apologies, I think I've resolved that build issue now with my latest commit. Can you update to the latest HEAD commit and try it once more?
Hmm, interesting. Can you link me to a repo where I can reproduce this?
I'm honestly not sure how to proceed here. If I do a import the default of `AsyncEventEmitter` in our code, it is undefined (since the `AsyncEventEmitter` typing uses the `export=`...
Unfortunately yes. We just went through the effort of removing that because of concerns we were impacting consumers of our code who might not want to use that setting. That...
I've actually been trying to do that locally but was continuing to get weird errors. So, will try and put some more thought into on Monday!