You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2018. It is now read-only.
Block comments (delimited by ###) are now allowed anywhere, including inline where they previously weren’t possible, thanks to @GeoffreyBooth. This provides support for static type annotations using Flow’s comments-based syntax. Closes CS2 Discussion: Features: Type Annotations #12 (at least, via this implementation; feel free to open new issues for other static type solutions you’d like to suggest).
There are no breaking-change pull requests in the pipeline. This means that unless people report any showstopper bugs with this release, this could be the last beta before 2.0.0 is released. So please try it in your projects and let us know if it’s ready. The sooner we get feedback saying that all is well (or that there are bugs we need to address) the sooner we can release 2.0.0.
If you encounter any issues, after first reviewing the breaking changes, please open an issue with “[CS2]“ in the title. Please don’t comment bug reports on this thread. Thanks!
The text was updated successfully, but these errors were encountered:
So, any reports of projects working well under 2.0.0-beta4?
As far as I can tell, we have two open bugs that need fixing before we can release 2.0.0, and there are WIP pull requests for both of them. See https://github.com/jashkenas/coffeescript/milestone/10. Now would be the time to let us know if there are any other issues that should be addressed before the 2.0.0 release.
The other task that I’d like to get addressed soonish, ideally before the 2.0.0 release, is jashkenas/coffeescript#4615: demo projects showing how to use CoffeeScript 2 with Webpack, Gulp, Babel etc. Even if you know nothing about the CoffeeScript codebase, if you can spare the time to whip up an example repo it would make a great addition to our documentation!
coffeescriptbot
changed the title
Progress as of August 2017: 2.0.0-beta4!
CS2 Discussion: Project: Progress as of August 2017: 2.0.0-beta4!
Feb 19, 2018
Hey everyone,
CoffeeScript 2.0.0-beta4 is released! Install it via:
npm install coffeescript@next
Since the last update, as of 2017-08-04 the following has been merged into the jashkenas/coffeescript
2
branch and released in 2.0.0-beta4:#
) are now output in the generated JavaScript, thanks to @GeoffreyBooth. You can see them in the examples in the docs.###
) are now allowed anywhere, including inline where they previously weren’t possible, thanks to @GeoffreyBooth. This provides support for static type annotations using Flow’s comments-based syntax. Closes CS2 Discussion: Features: Type Annotations #12 (at least, via this implementation; feel free to open new issues for other static type solutions you’d like to suggest)....
for objects) is now supported in JSX tags:<div {props...} />
, thanks to @zdenko.coffee
is improved, thanks to @cosmicexplorer. See breaking changes. This PR was started in 2015!SIGINT
andSIGTERM
signals when node is forked, thanks to @Gobie.await
in the REPL is now allowed without requiring a wrapper function, thanks to @connec.do super
is now allowed, thanks to @zdenko.super
likesuper.x.y
orsuper['x'].y
now work, thanks to @helixbass.props...
or...props
are both valid), thanks to @zdenko.return
andthrow
arguments, thanks to @helixbass._
, thanks to @xixixao.There are no breaking-change pull requests in the pipeline. This means that unless people report any showstopper bugs with this release, this could be the last beta before 2.0.0 is released. So please try it in your projects and let us know if it’s ready. The sooner we get feedback saying that all is well (or that there are bugs we need to address) the sooner we can release 2.0.0.
If you encounter any issues, after first reviewing the breaking changes, please open an issue with “[CS2]“ in the title. Please don’t comment bug reports on this thread. Thanks!
The text was updated successfully, but these errors were encountered: