Problem with Chrome Debugger when using spread operator

The following code works on the Simulator:

return Promise.all([fileInfo, ...(m.intoArray(setValuePromises))]);

but gives a Syntax error when I try to debug with Chrome.

[sahrens]

cc @amasad - missing transform?

[sebmck]

The JavaScript wouldn't be going through any transforms because it's just being executed natively.

[sahrens]

The JS is still transformed to generate the bundle which is loaded by chrome.

Still confused. Should it work ?

[sebmck]

It shouldn't work and there's probably no real way to make it work.

On Wednesday, 20 May 2015, Roger Gilliar notifications@github.com wrote:

Still confused. Should it work ?

Reply to this email directly or view it on GitHub
#1280 (comment)
.

Sebastian McKenzie

[ide]

@sebmck I believe it should work. RN deploys ES5... in theory with ES3 support RN could run in IE8 if we wanted. Something is going wrong with the transform that's causing Chrome to receive a maltransformed spread operator.

@RogerGL can you view the JS that is running in Chrome and see what the code around your Promise.all call looks like?

This is the complete method:

 var setContent = (result) => {
 var fileInfo = result[0];
 var setValuePromises = m.map((data) => {
 return Store.setValue(m.get(data, "fileName"), m.get(data, "content"));
 }, fileInfo);
 return Promise.all([fileInfo, ...(m.intoArray(setValuePromises))]);
 };

[ide]

@RogerGL, sorry - I meant the code that Chrome's web inspector shows under the Sources tab. Things like the arrow functions should be transformed into normal functions.

Chrome displays the code given in the previous posting.

This is the code from the index.ios.bundle file:

 var setContent = function(result) {
 var fileInfo = result[0];
 var setValuePromises = m.map(function(data) {
 return Store.setValue(m.get(data, "fileName"), m.get(data, "content"));
 }, fileInfo);
 return Promise.all([fileInfo, ...(m.intoArray(setValuePromises))]);
 }; 

[sahrens]

Hopefully this will be fixed when we switch to babel soon.

[ide]

@RogerGL: thanks. Looks like a transform bug.

The best workaround now is to write a manual array.concat call until the transform pipeline uses babel as @sahrens mentioned.

[sebmck]

@ide Oh right. Sorry for speaking out of turn. I thought he was referring to the dev tools console.

[amasad]

Yeah, I hate this discrepancy. JavaScript Core has rest param support whereas chrome doesn't. Pushing the switch to Babel shortly, and it should include this transform.