Rakudo.js update - hunting down failing roast tests
Currently I'm working to getting rakudo.js to pass (our choosen subset of tests) in Chrome rather then on node.js.
The way the process works is that the Perl 6 test files get compiled to JavaScript and bundled by the parcel with everything they needs to run. The bundling includes the setting, runtime and even the whole Rakudo compiler (tests use EVAL a lot).
As as side node it turns out that for debugging purposes node bundled-everything.js emulates running in the brow…