ES2015+?

It’s 2019, and ES2015+ features supports is getting better among modern browsers. Several patches from #2 already using some (mostly let/const).

So it would be great if we decide which of the features are ‘safe’ to use in whole project. But to select particular features we need to consider target platforms of IITC, as some of them could be limited.

Perhaps most universal approach would be to:

• Include some transpilling tool in our build chain.

[modos189]

Babel requires a node.js, which I would like to avoid.

I found a project that implements the Javascript interpreter on Python. As stated, he is not production ready, but it works.

And if there were no problems with connecting DukPy, I would prefer to choose TypeScript, not Babel. Because he too implements the capabilities of the new ES, but it also supports types.

[johnd0e]

One more question: JS Promise vs jQuery.Deferred().

Promise is not part of ES5, that’s why we begin to use jQuery.Deferred (https://github.com/iitc-project/ingress-intel-total-conversion/pull/1163).

But refactoring of game_status.js/map_data_request.js/redeeming.js/request_handling.js/search.js/send_request.js/… will demand more extensive promises using, so we should decide whether to stick to jQuery’s implementation, or switch to native JS’s.