acolytec3

I went back and reread your last comment and I was actually trying something slightly different so I tried your approach this morning but unfortunately I'm having the same sort...

Okay, went back to a clean slate and tried exactly the changes you noted above and I'm still getting the `not a constructor` error. I'm stumped. :thinking:

And I confirmed it's working fine when I look at your repo. I cloned it and built locally, using `npm link` to link it to my local branch with these...

Interesting... That may be a tricky one. What's especially remarkable is that you're using the same compiled output that I am. We just have some weird double declaration or something...

I definitely see the actual issue now, and I can see typescript intellisense seeing both the namespace and the named export but it's still not clear to me where typescript...

> > > > I am not sure what to make of the karma browser test failures. It seems to be complaining about a dist file. @acolytec3 are these karma...

> > > > > > > > > I am not sure what to make of the karma browser test failures. It seems to be complaining about a dist...

Can we close this for now and re-address if it starts failing again? It looks like some sort of fluke and the tests are all passing the past 2 weeks....

So I didn't realize we had left this one open but this was completed in #2379. Sorry we didn't see and merge this earlier! I'm going to close for now...

>When creating the VM, the evm property is cast as EVMInterface. If VM is created without injecting the EVM, it thus creates EVM, which should also be cast as such....