Skip to content

Conversation

@GeoffreyBooth
Copy link
Collaborator

Okay folks, this is it. Since 2.0.0-beta5, PRs that involved changes to the compiler have been:

Changes 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 from master, leaving just the generated output in the docs/v1 folder; the v1 source files will live on in the 1 branch (the mirror of how things were when we had the 2 branch and v1 was on master). If the v1 docs ever need updating again, we can generate new v1 docs on the 1 branch and copy the generated docs/v1 folder onto master, like I had been doing for the 2 branch.

Changes to the docs in this PR include updating the changelog, links, and getting rid of @next from coffeescript@next: http://rawgit.com/GeoffreyBooth/coffeescript/2.0.0/docs/v2/

So . . . are we ready?


* 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.
Copy link
Collaborator

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"

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah good point 😆

Copy link
Collaborator

@lydell lydell left a 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants