* Support ES2018 regex dotall flag
* Test in Node 9
* Alphabetize regex flags
* Split regex dotall test into its own file, use new feature detection method of loading it
* Update docs to explain compatibility for ES2018 and newer Node features
* Remove unnecessary paragraph
* Passthrough exponentiation operator; remove tests that are invalid JavaScript
* Treat **= as a passthrough assignment
* Get tests passing in Node 6
* Improve scoping
* Move exponentiation tests into their own file, now that it's filtered out by Cakefile
* Restore original test
* Make `node --harmony bin/cake test` pass on Node 9
Make classMaker() explicitly return an object
* Update Travis and AppVeyor to use --harmony and v9
* Test cases for #4852, get/set oddities
* Fix soak before accessor call to `get` or `set`
* Fixes#4852: More get/set cases; cleanup style
* Check for tokens' existence before referencing them
* fix#3921: inline function without parentheses used in condition
* add grammar rules
* fix issue #2343
* typos
* multiple 'else' in line
* close 'else if'
* First attempt at using AppVeyor
* Maybe it doesn't like the leading dot?
* Versions are an array
* Fix tests on Windows: for some reason, Windows requires `coffee` to be executed as `node coffee` (in the context of `spawnSync`, at least)
* Use npm@latest, see if that's less noisy
* Nevermind, only an issue on Node 6
* Better to see the NPM version before npm install
* Fix#4706: Comments before a PARAM_START token stay before that token
* Simplify nodes
* Add function-in-function test
* Fix#4706: Comments after class name should go after the identifier that's after `class`, not the variable assigned to
* Fix#4706: Top-level identifiers with trailing comments get wrapped in parentheses (around the comment too) so that Flow doesn't interpret it as a JavaScript label
* Cleanup
* If the source has parentheses wrapping an identifier followed by a block comment, output those parentheses rather than optimizing them away; this is a requirement of Flow, to distinguish from JavaScript labels
* More tests for Flow comments
* For local variables with trailing inline herecomments, output the comments up in the variable declarations line for Flow compatibility
* Fix#4706: Comments before a PARAM_START token stay before that token
* Simplify nodes
* Add function-in-function test
* Fix#4706: Comments after class name should go after the identifier that's after `class`, not the variable assigned to
* Fix#4706: Top-level identifiers with trailing comments get wrapped in parentheses (around the comment too) so that Flow doesn't interpret it as a JavaScript label
* Cleanup
* If the source has parentheses wrapping an identifier followed by a block comment, output those parentheses rather than optimizing them away; this is a requirement of Flow, to distinguish from JavaScript labels
* More tests for Flow comments
The handling of hoisted nodes in class bodies was incorrect, as the node
was being unwrapped *before* checking if it was hoisted, meaning nodes
that should have been hoisted would be output normally.
This affected `PassthroughLiteral`s as they were wrapped in a `Value`.
* Fix#4725: apply transpile option to require’d .coffee files
* Use the current module’s options if it has any, before going searching up the tree
* Don’t mutate passed-in options object
* If the REPL is run with `--transpile`, turn transpilation on for both the current REPL input and any files imported by that input
* Use the command.coffee machinery for parsing arguments
* Fix test for Windows
* Fix#4725: apply transpile option to require’d .coffee files
* Use the current module’s options if it has any, before going searching up the tree
* Don’t mutate passed-in options object
