Mike Cann

Did you ever solve this? Im having the same problem.

Ahh damn :( Some of us still have legacy projects to maintain!

I believe it is to do with trying to mock concrete classes instead of interfaces. If the concrete class throws an error in the constructor then you get this error.

Scratch all that, the problem was simply because I forgot to prepare on of the dependencies, doh!

Okay no worries, im having issues with some nuances of Typescripts typing structure: http://stackoverflow.com/questions/37381705/hoverboard-typings If I manage to get that sorted ill do just that!

Hmmm ye I was thinking about intersection types, not used them before. Ill have a play a little later and see.

Seems like a good idea to me!

For now I work around the solution with the following: ```ts archetype.onEntityRemoved.add((e) => { const actions = e.mesh.actions.filter((a) => a.trigger == ActionManager.OnPickTrigger); for (const action of [...actions]) e.mesh.actionManager.unregisterAction(action); }); ```...

> What do you think about these? Ye those could work.. I assume the cost of executing `onComponentAdded` `onComponentRemoved` for every component added or removed even if there isnt a...

> Does this make sense? Would this help you? Yes I like it but as you mention in your above addendum it could potentially cause some unexpected user errors. You...