Chad Hietala 8a320d53a5 Metadata object does not take in account resolveModuleSource() ...

This adds a failing test to illustrate the metadata object not reflecting what is returned from resolveModuleSource(). I might also not understand resolveModuleSource's purpose. However, this was the hook mentioned here https://github.com/babel/babel/issues/1602.

2015-06-09 14:26:33 -07:00

..

fixtures

use actual parameter reference for non-last default parameters - fixes #1690

2015-06-05 14:08:18 +01:00

_browser.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

remove useless generator test helpers

2015-05-31 21:26:22 +01:00

api.js

Metadata object does not take in account resolveModuleSource()

2015-06-09 14:26:33 -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

Small fixes to es7.functionBind and generation tests added.

2015-05-13 18:20:33 +03:00

path.js

fix test/core/path imports

2015-05-04 15:25:35 +01:00

traceur.js

fix traceur test blacklist

2015-06-09 03:48:22 +01:00

transformation.js

restructure testing infrastructure to be more modular

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

traverse.js

move traverse replace test up

2015-05-15 18:35:15 +01:00

types.js

restructure testing infrastructure to be more modular

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

util.js

make path patterns used by only and ignore **very** liberal, this will ease a lot of pain in dealing with them

2015-05-15 02:33:40 +01:00