Comparing 2.0.1...2.0.2 · jashkenas/coffeescript
Commits on Oct 3, 2017
-
Fix #4727: Tests failing in Windows (#4731)
* ? * ?? * Revert the coffee.EXE approach * Explicitly define the PATH to include only the folders we need * Get spawnSync working in Windows * Simplify test to be cross-platform
Commits on Oct 5, 2017
-
* 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
Commits on Oct 7, 2017
Commits on Oct 19, 2017
-
Fix #4706: Flow generics (#4736)
* 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
-
Fix #4747: Flow local variables (#4753)
* 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