Please make a new release for coffee-script-source with CoffeeScript 2.0.1

[joeldrapper]

The documentation says, “This library depends on the coffee-script-source gem which is updated any time a new version of CoffeeScript is released.”

Several new versions of CoffeeScript have been released, the latest of which is version 2.0.1.

[kWhittington]

Pretty please.

[gobijan]

I created this pull request to update the coffee-script-source gem to version 2.
#23

[gobijan]

It just got merged. Since CoffeeScript 2 transpiles into ES6 (see http://coffeescript.org/#whats-new-in-coffeescript-2): Is another 6to5 step wanted?

[rafaelfranca]

Oh, yeah, we will need es5 code.

[gobijan]

You have any recommendation here? Should this be up to the user wether to enable 6to5 transpiling or not? I saw that in the uglifier gem description https://github.com/babel/ruby-babel-transpiler is given as an example for 6to5 transpiling.

[joeldrapper]

I saw the @gobijan’s PR got merged. Is there anything holding back the gem release?

[gobijan]

Anyone knows what's the current "official" sentiment in regard to coffeescript in rails?
Will it still be the default?
Is ES6 now preferred?

I saw that basecamp released stimulusjs (https://github.com/stimulusjs/stimulus) and it's written in Typescript.
Rails action cable on the other hand is written in Coffeescript (v1?).

I contributed a patch that enables the automatic build of the coffee-script-source gem supporting coffeescript2 (#23) and it got merged. But there is no new release of that gem as you can see in this issue: #22 .

I did not get any feedback yet and I don't know what the plans are in regard to Coffeescript 1 vs 2 vs ES6 vs Typescript.

What direction is the Rails core team heading here? @rafaelfranca @dhh

[dhh]

Webpacker is in contention to become the preferred/default JavaScript compiler for Rails 6. With that comes the freedom to use whatever transpiler steps available through Webpack and Babel. Which means that in many ways it doesn’t really matter where “things are going”, you can write your JS in whatever flavor you please, and it will all compile together harmoniously. That being said, CoffeeScript’s previous advantage over vanilla JS has shrunk considerably after ES2015 was released. I don’t think as many developers are going to be drawn to CS now as were in the past because of this. But that’s a triumph of CS! It helped show the way forward for vanilla JS, so we should celebrate its achievement rather than mourn its decline.

…

On Jan 7, 2018, at 07:57, Bijan Rahnema ***@***.***> wrote: Anyone knows what's the current "official" sentiment in regard to coffeescript in rails? Will it still be the default? Is ES6 now preferred? I saw that basecamp released stimulusjs (https://github.com/stimulusjs/stimulus) and it's written in Typescript. Rails action cable on the other hand is written in Coffeescript (v1?). I contributed a patch that enables the automatic build of the coffee-script-source gem supporting coffeescript2 (rails/ruby-coffee-script#23) and it got merged. But there is no new release of that gem as you can see in this issue: rails/ruby-coffee-script#22 . I did not get any feedback yet and I don't know what the plans are in regard to Coffeescript 1 vs 2 vs ES6 vs Typescript. What direction is the Rails core team heading here? @rafaelfranca @dhh — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[n-rodriguez]

Hi! Even if Webpack seems to be the future of assets management in Rails, it would be nice to have this PR merged to ease the transition from assets pipeline to Webpack.

my 2 cents. thank you!

[guilleiguaran]

@n-rodriguez I don't see any PR open related to this, feel free to open one upgrading the version of CS

[n-rodriguez]

@guilleiguaran actually it's already merged: #23.
It just needs a new release.