Search

Clear search

Close search

Main menu

Google apps

traceur-compiler-discuss

1–30 of 245

0 selected

9/2/20

Running --script, but for a whole directory

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

unread,

Running --script, but for a whole directory

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

9/2/20

Mehrdad Shokri, Sander Elias2

1/6/18

Relevence to Babel

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

unread,

Relevence to Babel

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

1/6/18

johnjbarton johnjbarton

4/10/16

Single-file 'System' for browsers via npm, bin/BrowserSystem.js

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

unread,

Single-file 'System' for browsers via npm, bin/BrowserSystem.js

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

4/10/16

johnjbarton johnjbarton

3/26/16

Error: EMFILE, too many open files on Mac -> ulimit -n 4096

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

unread,

Error: EMFILE, too many open files on Mac -> ulimit -n 4096

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

3/26/16

Owen Densmore, John J Barton4

3/8/16

es6-module-loader: using traceur to only transpile modules

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

unread,

es6-module-loader: using traceur to only transpile modules

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

3/8/16

Lucas Dixon, John J Barton4

10/30/15

building and running tests

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

unread,

building and running tests

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

10/30/15

Michael McGlothlin

10/23/15

Problem with constructors and rest parameters?

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

unread,

Problem with constructors and rest parameters?

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

10/23/15

Michael McGlothlin, John J Barton3

10/13/15

strong mode stripping?

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

unread,

strong mode stripping?

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

10/13/15

Danilo Araújo Silva, John J Barton4

6/18/15

How to use await with traceur compiler on the fly?

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

unread,

How to use await with traceur compiler on the fly?

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

6/18/15

João Fernandes, Erik Arvidsson2

5/27/15

Unexpected token ":"

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

unread,

Unexpected token ":"

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

5/27/15

Илья Сырцов, Erik Arvidsson4

4/30/15

Incorrect code coloring when using string templates in traceur

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

unread,

Incorrect code coloring when using string templates in traceur

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

4/30/15

Илья Сырцов, Erik Arvidsson2

4/29/15

How to try SoundScript "use stricter" and "use stricter+typed" modes in Traceur?

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

unread,

How to try SoundScript "use stricter" and "use stricter+typed" modes in Traceur?

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

4/29/15

Karthik Bose, John J Barton3

4/24/15

traceur on-the-fly results in error (ReferenceError: webLoader is not defined)

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

unread,

traceur on-the-fly results in error (ReferenceError: webLoader is not defined)

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

4/24/15

João Fernandes, Erik Arvidsson5

3/23/15

Traceur and Typescript

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

unread,

Traceur and Typescript

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

3/23/15

3/3/15

PSA: Stricter classes in 0.86

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

unread,

PSA: Stricter classes in 0.86

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

3/3/15

gaurav khurana, … John J Barton3

2/27/15

call spread operator giving error in node console

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

unread,

call spread operator giving error in node console

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

2/27/15

Blake McBride, Erik Arvidsson7

2/25/15

FROM atscript or ES6?

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

unread,

FROM atscript or ES6?

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

2/25/15

John J Barton, Erik Arvidsson2

2/19/15

Adding location values to parse trees.

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

unread,

Adding location values to parse trees.

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

2/19/15

raul.m...@gmail.com, Erik Arvidsson4

2/18/15

for (let i of new F) {} not valid syntax?

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

unread,

for (let i of new F) {} not valid syntax?

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

2/18/15

Si, … John J Barton6

2/16/15

Can't enable experimental features using traceur.options.experimental=true;

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

unread,

Can't enable experimental features using traceur.options.experimental=true;

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

2/16/15

johnjbarton johnjbarton, Si2

2/13/15

Options passed by argument, no global 'options'

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

unread,

Options passed by argument, no global 'options'

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

2/13/15

João Fernandes, Erik Arvidsson3

2/12/15

undefined definition on the transpiled code

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

unread,

undefined definition on the transpiled code

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

2/12/15

João Fernandes, Erik Arvidsson3

2/4/15

inline arrow function uses additional parameters

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

unread,

inline arrow function uses additional parameters

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

2/4/15

João Fernandes, Erik Arvidsson3

2/4/15

Constants and value inlining

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

unread,

Constants and value inlining

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

2/4/15

Guido Tapia, … Erik Arvidsson4

1/29/15

Some questions from an Angular user who is confused with types, typescript, atscript

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

unread,

Some questions from an Angular user who is confused with types, typescript, atscript

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

1/29/15

Nicolas Badia, John J Barton3

1/27/15

Prevent traceur from removing the comments

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

unread,

Prevent traceur from removing the comments

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

1/27/15

Dev F, Erik Arvidsson4

1/21/15

Turning on async functions experimental feature

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

unread,

Turning on async functions experimental feature

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

1/21/15

John J Barton, Erik Arvidsson4

1/12/15

Runtime options

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

unread,

Runtime options

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

1/12/15

Dickson Wong, Erik Arvidsson2

1/12/15

Behavior of `let` inside a loop

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

unread,

Behavior of `let` inside a loop

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

1/12/15

Gil Tayar, … Guy Bedford5

12/29/14

importing modules and the <script> tag

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

unread,

importing modules and the <script> tag

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

12/29/14