CS2 Discussion: Project: Progress as of February 2017: 2.0.0-alpha1!

[coffeescriptbot]

From @GeoffreyBooth on 2017-02-22 06:03

Hey everyone,

CoffeeScript 2.0.0-alpha1 is released! Install it via: npm install coffeescript@next

You may notice that it’s not at coffee-script. The powers that be at NPM were kind enough to release the coffeescript package name to us. Since no one really spells CoffeeScript with a hyphen anymore, it seemed a better choice. It has both the old versions and 2.0.0-alpha1, and will be the home for future versions. coffee-script will stay 1.x-only, in case anyone installs coffee-script and expects a compiler that outputs ES3.

Since the last update, as of 2017-02-21 the following has been merged into the jashkenas/coffeescript 2 branch:

• Classes, including idiomatic output for both the class and super keywords, thanks to @connec.
• Redesigned docs for v2, thanks to @GeoffreyBooth.
• Refactored Cake tasks adding watch modes to building the compiler, thanks to @GeoffreyBooth.

As of December, we had accomplished:

• Tagged template literals, thanks to @greghuc.
• Interpolated strings are now output as template literals (ES backtick syntax), thanks to @greghuc.
• Triple-backtick operator and escaped backticks in embedded JavaScript, thanks to @GeoffreyBooth.
• The browser tests work again, thanks to @GeoffreyBooth.

And as of November, we had accomplished:

• Async/await, thanks to @GabrielRatener.
• Arrow functions, function default parameters and function rest parameters, thanks to @GeoffreyBooth.
• Splats in arrays and function calls are output using ES2015 syntax, thanks to @connec.
• Computed properties are output using ES2015 syntax, thanks to @connec.
• Octal and binary literals are output as-is, thanks to @JimPanic.
• CoffeeScript is stricter about whitespace thanks to @eelco, and Literate CoffeeScript now understands Markdown thanks to @billymoon.
• Support for ES2015 for…of is implemented, thanks to @atg.
• Bugs were fixed by @alangpierce, @shreeve, @JimPanic, @GeoffreyBooth and others. Also thanks for feedback from @lydell and @jashkenas.

---

There are still a handful of features yet to implement, including destructuring and getters/setters. Help with those is most welcome, but if you don’t have time for that, you could also help out by trying 2.0.0-alpha1 in your projects. Please review the breaking changes first, and if you think there’s a bug, please open an issue with “[CS2]“ in the title. Please don’t comment bug reports on this thread. Thanks!

[coffeescriptbot]

From @jiyinyiyong on 2017-02-22 08:14

Any clarification for npm info coffeescript?

     '1.12.4',
     '2.0.0-alpha1',
     '99.999.9999',
     '99.999.99999' ],

[coffeescriptbot]

From @GeoffreyBooth on 2017-02-22 16:33

The 99 versions are leftovers from the previous package, which was just a warning that you had misspelled CoffeeScript.

[coffeescriptbot]

From @jiyinyiyong on 2017-02-22 16:45

Will it affect 2.0.0? It's strange that npm does not pick the higher version which is 99.x.

[coffeescriptbot]

From @lydell on 2017-02-22 16:55

npm install foo is just a shorthand for npm install foo@latest. It is up to the publisher to decide what the latest tag should point to.

[coffeescriptbot]

From @nickdima on 2017-02-22 23:22

Great job everybody! I'm curious what new oportunities will CS2 bring around tooling (stuff like linting, auto-formatting, etc.) and how it could benefit from the babel & co. ecosystem.

[coffeescriptbot]

From @scottwarren on 2017-02-23 05:42

What are your guys thoughts on outputting something when people install coffee-script to let them know that the "latest" is a package name change, and now lives at coffeescript instead?

[coffeescriptbot]

From @GeoffreyBooth on 2017-02-23 05:59

@scottwarren Maybe after 2.0.0 final is released, that's a thought.

[coffeescriptbot]

From @lydell on 2017-02-23 06:44

@nickdima Basically none. CS2 uses the same architecture as CS1.

[coffeescriptbot]

From @DomVinyard on 2017-02-24 10:34

awesome! well done guys, we're lucky to have you. Now, I guess I need to start a new project to test all this stuff out on! Hmmm... choices, choices... x

[coffeescriptbot]

From @YamiOdymel on 2017-02-24 13:44

I'm using CoffeeScript 2 with WebPack and Vue.js and it works great! (except for the spread operator)

[coffeescriptbot]

From @laurentpayot on 2017-02-24 17:52

To use CS2 with webpack I simply had to create a symbolic link from coffeescript to coffee-script in my node_modules folder. It's working fine. I see that @YamiOdymel already created an issue in coffee-loader: webpack-contrib/coffee-loader#27 😄

[coffeescriptbot]

From @GeoffreyBooth on 2017-02-24 18:03

@YamiOdymel Thanks! As for the spread operator, that seems like something that should be implemented as part of destructuring (coffeescript6/discuss#69) which I’ve started a branch for if you’d like to take a crack at it . . . 😉

[coffeescriptbot]

From @GeoffreyBooth on 2017-02-26 16:00

Has anyone tried CS2 on an existing project? What changes, if any, did you need to make to your code?