diff --git a/.babelrc b/.babelrc
new file mode 100644
index 0000000000..002b4aa0d5
--- /dev/null
+++ b/.babelrc
@@ -0,0 +1,3 @@
+{
+ "presets": ["env"]
+}
diff --git a/Cakefile b/Cakefile
index f7145f2188..e8629054e8 100644
--- a/Cakefile
+++ b/Cakefile
@@ -70,16 +70,9 @@ transpile = (code) ->
babel = require 'babel-core'
presets = []
# Exclude the `modules` plugin in order to not break the `}(this));`
- # at the end of the above code block.
+ # at the end of the `build:browser` code block.
presets.push ['env', {modules: no}] unless process.env.TRANSFORM is 'false'
- babelOptions =
- presets: presets
- sourceType: 'script'
- { code } = babel.transform code, babelOptions unless presets.length is 0
- # Running Babel twice due to https://github.com/babel/babili/issues/614.
- # Once that issue is fixed, move the `babili` preset back up into the
- # `presets` array and run Babel once with both presets together.
- presets = if process.env.MINIFY is 'false' then [] else ['babili']
+ presets.push 'minify' unless process.env.MINIFY is 'false'
babelOptions =
compact: process.env.MINIFY isnt 'false'
presets: presets
@@ -100,7 +93,7 @@ testBuiltCode = (watch = no) ->
buildAndTest = (includingParser = yes, harmony = no) ->
process.stdout.write '\x1Bc' # Clear terminal screen.
- execSync 'git checkout lib/*', stdio: [0,1,2] # Reset the generated compiler.
+ execSync 'git checkout lib/*', stdio: 'inherit' # Reset the generated compiler.
buildArgs = ['bin/cake']
buildArgs.push if includingParser then 'build' else 'build:except-parser'
@@ -494,20 +487,28 @@ task 'test:integrations', 'test the module integrated with other libraries and e
# Node modules are required as part of the compiler (as opposed to the tests)
# and that therefore the compiler will run in a browser environment.
tmpdir = os.tmpdir()
- try
- buildLog = execSync "./node_modules/webpack/bin/webpack.js
- --entry=./
- --output-library=CoffeeScript
- --output-library-target=commonjs2
- --output-path=#{tmpdir}
- --output-filename=coffeescript.js"
- catch exception
- console.error buildLog.toString()
- throw exception
-
- builtCompiler = path.join tmpdir, 'coffeescript.js'
- CoffeeScript = require builtCompiler
- global.testingBrowser = yes
- testResults = runTests CoffeeScript
- fs.unlinkSync builtCompiler
- process.exit 1 unless testResults
+ webpack = require 'webpack'
+ webpack {
+ entry: './'
+ output:
+ path: tmpdir
+ filename: 'coffeescript.js'
+ library: 'CoffeeScript'
+ libraryTarget: 'commonjs2'
+ }, (err, stats) ->
+ if err or stats.hasErrors()
+ if err
+ console.error err.stack or err
+ console.error err.details if err.details
+ if stats.hasErrors()
+ console.error error for error in stats.compilation.errors
+ if stats.hasWarnings()
+ console.warn warning for warning in stats.compilation.warnings
+ process.exit 1
+
+ builtCompiler = path.join tmpdir, 'coffeescript.js'
+ CoffeeScript = require builtCompiler
+ global.testingBrowser = yes
+ testResults = runTests CoffeeScript
+ fs.unlinkSync builtCompiler
+ process.exit 1 unless testResults
diff --git a/docs/v2/index.html b/docs/v2/index.html
index c4ed852cc4..3df4ca49de 100644
--- a/docs/v2/index.html
+++ b/docs/v2/index.html
@@ -527,12 +527,13 @@
Try CoffeeScriptOverviewCoffeeScript 2
+ CompatibilityInstallationUsageLanguage Reference
diff --git a/documentation/sections/coffeescript_2.md b/documentation/sections/coffeescript_2.md
index 7cf457de3c..72b66b07fc 100644
--- a/documentation/sections/coffeescript_2.md
+++ b/documentation/sections/coffeescript_2.md
@@ -2,16 +2,12 @@
### What’s New In CoffeeScript 2?
-The biggest change in CoffeeScript 2 is that now the CoffeeScript compiler produces modern, ES2015+ JavaScript. A CoffeeScript `=>` becomes an ES `=>`, a CoffeeScript `class` becomes an ES `class` and so on. With the exception of [modules](#modules) (`import` and `export` statements) and [JSX](#jsx), all the ES2015+ features that CoffeeScript supports can run natively in Node 7.6+, meaning that Node can run CoffeeScript’s output without any further processing required. You can [run the tests in your browser](http://coffeescript.org/v<%= majorVersion %>/test.html) to see if your browser can do the same; Chrome has supported all features since version 55.
-
-Support for ES2015+ syntax is important to ensure compatibility with frameworks that assume ES2015. Now that CoffeeScript compiles classes to the ES `class` keyword, it’s possible to `extend` an ES class; that wasn’t possible in CoffeeScript 1. Parity in how language features work is also important on its own; CoffeeScript “is just JavaScript,” and so things like [function parameter default values](#breaking-changes-default-values) should behave the same in CoffeeScript as in JavaScript.
-
-Many ES2015+ features have been backported to CoffeeScript 1.11 and 1.12, including [modules](#modules), [`for…of`](#generator-iteration), and [tagged template literals](#tagged-template-literals). Major new features unique to CoffeeScript 2 are support for ES2017’s [async functions](#async-functions) and for [JSX](#jsx). More details are in the [changelog](#changelog).
+The biggest change in CoffeeScript 2 is that now the CoffeeScript compiler produces modern JavaScript syntax (ES6, or ES2015 and later). A CoffeeScript `=>` becomes a JS `=>`, a CoffeeScript `class` becomes a JS `class` and so on. Major new features in CoffeeScript 2 include [async functions](#async-functions) and [JSX](#jsx). You can read more in the [changelog](#changelog).
There are very few [breaking changes from CoffeeScript 1.x to 2](#breaking-changes); we hope the upgrade process is smooth for most projects.
-### Why CoffeeScript When There’s ES2015?
+### Why CoffeeScript When There’s ES6?
CoffeeScript introduced many new features to the JavaScript world, such as [`=>`](#fat-arrow) and [destructuring](#destructuring) and [classes](#classes). We are happy that ECMA has seen their utility and adopted them into ECMAScript.
-CoffeeScript’s intent, however, was never to be a superset of JavaScript. One of the guiding principles of CoffeeScript has been _simplicity:_ not just removing JavaScript’s “bad parts,” but providing an elegant, concise syntax that eschews unnecessary punctuation whenever possible, to make code easier to read and reason about. This benefit of CoffeeScript remains, even in an ES2015 world.
+CoffeeScript’s intent, however, was never to be a superset of JavaScript. One of the guiding principles of CoffeeScript has been _simplicity:_ not just removing JavaScript’s “bad parts,” but providing an elegant, concise syntax that eschews unnecessary punctuation whenever possible, to make code easier to read and reason about. This benefit of CoffeeScript remains, even in an ES2015+ world.
diff --git a/documentation/sections/command_line_interface.md b/documentation/sections/command_line_interface.md
index 1f168e8c3d..3c13142db8 100644
--- a/documentation/sections/command_line_interface.md
+++ b/documentation/sections/command_line_interface.md
@@ -5,6 +5,7 @@ Once installed, you should have access to the `coffee` command, which can execut
| Option | Description |
| --- | --- |
| `-c, --compile` | Compile a `.coffee` script into a `.js` JavaScript file of the same name. |
+| `-t, --transpile` | Pipe the CoffeeScript compiler’s output through Babel before saving or running the generated JavaScript. Requires `babel-core` to be installed, and options to pass to Babel in a `.babelrc` file or a `package.json` with a `babel` key in the path of the file or folder to be compiled. See [Transpilation](#transpilation).
| `-m, --map` | Generate source maps alongside the compiled JavaScript files. Adds `sourceMappingURL` directives to the JavaScript as well. |
| `-M, --inline-map` | Just like `--map`, but include the source map directly in the compiled JavaScript files, rather than in a separate file. |
| `-i, --interactive` | Launch an interactive CoffeeScript session to try short snippets. Identical to calling `coffee` with no arguments. |
@@ -16,10 +17,10 @@ Once installed, you should have access to the `coffee` command, which can execut
| `-e, --eval` | Compile and print a little snippet of CoffeeScript directly from the command line. For example: