Jan Biedermann

At this stage the following works: ```ruby require 'engine' # Engine now allow access to globalThis, so in the browser for example Engine.history.length # -> 2 ``` manually in the...

further works: ``` require 'engine' Engine.history.class.name # -> Engine::History a = Engine::ArrayBuffer.new() a.class.name # -> Engine::ArrayBuffer ``` the last one in js: ``` Opal.Engine.$const_get('ArrayBuffer').$new().$class().$name() // -> 'Engine::ArrayBuffer' ```

Possibly, its handy for testing things, as its the goal to have automatic, easy and compact access to JS APIs and values. Once everything is working i may make that...

For correctness when using Engine for testing the bridges proeprties must be accessed by [], eg: ``` Engine[:history] Engine[:history][:length] Engine[:history].back ``` May work more or less, anymway Continuing from here...

 Try the same with assignment, how we use it

 Not so tiny at all

@rubyFeedback regarding #2569, when working on it and looking into ruby source to get compatibility right, i noticed, that the current approach using regexps will never be sufficient, due to...

Thanks, it still needs some time until i have time to continue working on it

This issue applies to opal likewise, when the compiler is run in node. V8 cannot optimize, because the method is too big.

Usually i just take the production build for testing. If you need a special configuration for testing, you may provide a extra webpack test configuration file (where the other webpack...