-
Notifications
You must be signed in to change notification settings - Fork 2k
2.0.0 #4701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0.0 #4701
Conversation
… the v1 docs need to be rebuild in the future, that can be done on the `1` branch and copied over; simplify folder tree
… reflect that the v2 docs are now the primary docs, and the v1 docs only live under /v1/
|
|
||
| * Added `--transpile` flag or `transpile` Node API option to tell the CoffeeScript compiler to pipe its output through Babel before saving or returning it; see [Transpilation](#transpilation). Also changed the `-t` short flag to refer to `--transpile` instead of `--tokens`. | ||
| * Always populate source maps’ `sourcesContent` property. | ||
| * Bugfixes for destructuring and for comments in JSX. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we mention that people might also want to read through the changelogs for the 2.0 betas below? So nobody ends up thinking like "WTF is that it for a 2.0? Not much of a change really"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah good point 😆
lydell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 From me. I think we're ready to go!
Okay folks, this is it. Since 2.0.0-beta5, PRs that involved changes to the compiler have been:
transpileflag/optionsourcesContentproperty as part of source map #4698: source maps’sourcesContentpropertyChanges to the docs and build process have included a new separate page with a CoffeeScript 2 announcement, a big new section about transpilation, and revisions to lessen the “ES2015+” jargon in favor of plainer terms like “modern JavaScript.” Commits are now tested via Travis CI, and the docs have Google Analytics.
This PR makes the v2 docs the primary docs, with the v1 docs living on under
/v1/. I also updated the v1 docs’ links and changed the “2 is coming” text. In this PR I removed the v1 docs source files frommaster, leaving just the generated output in thedocs/v1folder; the v1 source files will live on in the1branch (the mirror of how things were when we had the2branch and v1 was onmaster). If the v1 docs ever need updating again, we can generate new v1 docs on the1branch and copy the generateddocs/v1folder ontomaster, like I had been doing for the2branch.Changes to the docs in this PR include updating the changelog, links, and getting rid of
@nextfromcoffeescript@next: http://rawgit.com/GeoffreyBooth/coffeescript/2.0.0/docs/v2/So . . . are we ready?