Amjad Masad a540cbe801 Failing test with return not on the same line as it's expression ...

Note that this is not a parenthesis issue but this was the easiest way
to reproduce it. I ran into it when testing generators with `retainLines`
and the generated `return` statement (replacing yeild) was printed on
the line preceding the expression being yielded.

2015-04-30 05:06:56 -07:00

..

fixtures

Failing test with return not on the same line as it's expression

2015-04-30 05:06:56 -07:00

_browser.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

_generator-helpers.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

_helper.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

_transformation-helper.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

api.js

add extra transform option

2015-04-15 14:59:26 -07:00

bin.js

fix test tmp dir cleanup

2015-04-23 21:27:14 +03:00

browserify.js

Update core-js to ^0.8.1

2015-04-03 18:38:33 +09:00

esnext.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

generation.js

Add failing test for printing comments with retainLines option

2015-04-29 14:40:23 -07:00

kangax.js

rename es6.blockScopingTDZ to es6.spec.blockScoping

2015-03-30 16:52:58 +11:00

test262.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

traceur.js

traceur upstream sync

2015-04-02 02:21:12 +11:00

transformation.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

traverse.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

types.js

restructure testing infrastructure to be more modular

2015-03-28 01:21:48 +11:00

util.js

wrap non-arrays/strings/falsys in an array in util.list - fixes babel/babelify#69

2015-04-04 02:40:09 +11:00