-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Traceur to the latest version #79
Comments
A pull request would be welcome. Otherwise I probably should get around to #45 so everyone can bring their own Traceur. |
+1 |
I didn't even think there was an @domenic That would consist of bumping the version in |
@jmm yep. IIRC the way Traceur handles options has changed pretty drastically. |
@domenic Ok, thanks. It would be really nice if there was a changelog for traceur. |
@domenic I started working on this but quickly got into the weeds. Just doing this currently fails with node v0.10.32 (linux) / traceur v0.0.82: var
vm = require('vm'),
fs = require('fs'),
traceur = require('traceur');
vm.runInNewContext(
fs.readFileSync(traceur.RUNTIME_PATH)
); Result:
See nodejs/node-v0.x-archive/issues/9121. So that's interfering with some of the tests (e.g. |
Ok, I worked around the |
@domenic In |
@thlorenz can probably give a better idea on what the procedure is for those kind of tests. I agree they are fragile and brittle. However they have caught several regressions too :-/. |
Maybe a start would be: I think it's probably fine if you rebaseline them to the latest results. In the past the things they've caught have been e.g. empty source maps or source maps with wrong paths. |
Hi,
If I'm not mistaken es6ify is currently using Traceur 0.0.79 and there is a newer version available, 0.0.81. That one seems to solve some weird issues we have in our project so it would be awesome if we can have es6ify updated to that version.
Cheers!
The text was updated successfully, but these errors were encountered: