does not work when using with new `traceur-runtime.js` about benchpress HOT 3 CLOSED

Thanks, will look into this.

from benchpress.

Getting rid of traceur-runtime would be nice since it's more bytes, and since it's adding junk to the global object. Perhaps it's worth building a simplified DI for benchpress.

The auto-running context (ie benchmark runs in its own window or iframe) doesn't automatically solve the problem, because there still needs to be a runner present with the benchmark, to actually execute the code, time the tests, collect results, dispatch result events, etc.

I opened #24 with a proposal to properly address this issue, without giving up on DI altogether. In the meantime, I'll merge a fix that renames the $traceurRuntime and System globals during the build process so that they don't collide.

from benchpress.

Published to npm @0.2.2

from benchpress.