[Iced3] ES2015 modules support

[laurentpayot]

Hello there, a little question.

Since version 1.11 CoffeeScript supports ES2015 import and export syntax by producing an import or export statement in the resulting output. We have to add a layer of transpiler like babel or target ES6 to make it work, just like Iced3. But in Iced3, with babel, when I use the import syntax I get error: reserved word 'import'.

Is the IcedCoffeeScript codebase moving away from CoffeeScript on this point ?

[laurentpayot]

I've just noticed #194 but it doesn't seem to work…

[maxtaco]

I'll try to cut a release today. We just haven't released in a bit. Thanks!

[laurentpayot]

Ah yes it has not been released yet and I have issues building it (Error: Cannot find module 'iced-runtime-3'). Thanks @maxtaco!

[maxtaco]

Ok, should be live in v111.1.1

That's a lot of 1s!

Big thanks to @zapu who did all of the work.

[laurentpayot]

ES2015 imports are now working when using promises.
In order to use use async/defer, I have to install the iced-runtime-3 module. But once this module installed ES2015 imports are not working anymore.

@maxtaco Is a new release also needed for iced-runtime-3?

[maxtaco]

I didn't think so. I wonder what is up.

On Tuesday, November 15, 2016, Laurent Payot notifications@github.com
wrote:

ES2015 imports are now working when using promises.
In order to use use async/defer, I have to install the iced-runtime-3
module. But once this module installed ES2015 imports are not working
anymore.

@maxtaco https://github.com/maxtaco Is a new release also needed for
iced-runtime-3?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#198 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05__2SAvupqM8_Tgft5-WMOSghQ5NVks5q-d3TgaJpZM4Kyo5f
.

[zapu]

Weird, maybe installing iced-runtime-3 overwrites iced-coffee-script with a different version?

[maxtaco]

It really shouldn't. I am st a conference today so might not get a chance
to look right away.

On Tuesday, November 15, 2016, Michał Zochniak notifications@github.com
wrote:

Weird, maybe installing iced-runtime-3 overwrites iced-coffee-script with
a different version?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#198 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_8vsoasmmwiYbKOcVtBG_5-OA_Vfks5q-d5TgaJpZM4Kyo5f
.

[laurentpayot]

By the way I'm using iced3 -c script.coffee && babel-node script.js for my tests...

[zapu]

Hm, but won't iced3 -c compile just the script.coffee, so anything that script.js tries to import might not be compiled?

[laurentpayot]

I'm importing "standard" js (Firebase modules). And I'm also struggling to get any result from Firebase createUser() (that returns a promise) with the await/defer syntax. Not to mention catching errors…

[zapu]

async/defer is "just" a syntactic sugar for callback based asynchronous functions. So in theory you could try to do something like await promise_obj.then defer result but I'm not sure how this would turn out in your code. It might make more sense to just use the promise normally and pass anonymous functions as arguments to then.

[zapu]

I will try to experiment with iced3 -c and babel-node once I get off work, in few hours.

[laurentpayot]

Thank you so much @zapu, it really helped!
Now I'm using something like
await promise_obj.then(defer result).catch((error) -> console.log(error.message))
in a synchronous-like way of coding. Amazing 😃

[laurentpayot]

I still have the ES2015 import issue with await/defer, I get error: import statements must be at top-level scope, if it helps you…
Thanks again for your time!