traceur-compiler-discuss

I want to run the compiler like traceur --script src/in.js --out run/out.js but I want to do it for

Traceur was a tool that compiled es6 to es5. As all browsers now support es6 out of the box, there is

I changed the way traceur works in the browser. I believe that the bootstrap.js solution still works,

Just FYI: While compiling today I hit an error Error: EMFILE, too many open files The Internets

No, remove all of the other options, include only outputLanguage: es6. On Mon, Mar 7, 2016 at 9:33 AM

Hi Lucas, which version of node are you running? On Thu, Oct 29, 2015 at 8:41 PM, Lucas Dixon <

Using Node 4.2.1 and Traceur 0.91. I noticed an occasional problem when trying to use code converted

The problem is mostly that with strong mode enabled the transpiled version fails if the system

Two approaches more closely match practical web usage and work with Traceur: 1) Transcode on the

Type annotations are not supported in arrow functions. I just tried it in TypeScript, and your code

The code editor is using CodeMirror. We are not using traceur for syntax highlighting. On Wed, Apr 29

It is not implemented yet. We do support most of the TS type syntax (but not checked) using the --

This should be fixed and I published a new version. jjb On Thu, Apr 23, 2015 at 9:40 AM, John J

Thanks for the clarification erik On Mar 23, 2015 8:04 PM, "Erik Arvidsson" <arv@

To better align with ES6 we've added a bunch of restrictions related to this and super in classes

The example compiles: http://google.github.io/traceur-compiler/demo/repl.html#function%20myfunc()%20%

Thanks. I understand now. Appreciate the help! On Wednesday, February 25, 2015 at 4:18:18 PM UTC-6,

I'm not sure I follow. Before we had parseStatement etc we used null locations. One problem I

https://github.com/google/traceur-compiler/pull/1743 On Wed, Feb 18, 2015 at 10:09 AM, Erik Arvidsson

FYI: By experimentation, the following also seems to work: $traceurRuntime.options = new traceur.util

Hi John, Would this explain the problem I'm having enabling experimental features, described here

Done https://github.com/google/traceur-compiler/issues/1733 Thanks On 12 February 2015 at 18:44, Erik

I'll run JSLint against the optimized code and check if the warning goes away. Thanks Erik. On 4

Thanks Erik, My question is, so if I want to use traceur non uglified output, I need to preserve the

All the "works" above can be seen at http://goo.gl/TdSnwF Wow, thanks for the great reply

Thanks for the quick answer. From your explanation, I can understand that it would be a significant

Thanks you! Since I'm using systemjs, had to set System.traceurOptions System.traceurOptions.

I don't think we need to support those any more. All our runtime code uses toPropertyName to

This has been fixed: https://github.com/google/traceur-compiler/issues/1567 On Sun, Jan 11, 2015 at 9

I think you can be future compatible - surely the way to do this would be to have <script> tags