I also noticed that there was missing test coverage for builtin types,
so I added a test for that, which includes the newly added type as well
as the other existing types.
* Use browserslist to parse browsers from query.
* Update README.
* Use int values.
* Allow `isPluginRequired` use browserslist queries.
* Fix conflicts during different versions merging.
* Add tests for browserslist queries.
* Early return for getTargets.
* Update README: Describe `browsers` option.
* fix doc [skip ci]
* Move to dependencies [skip ci]
* Remove unused const.
* Use doublequotes for strings.
* Add Caveat section to Readme.md
The Caveat section details some known issues and workaround when targeting specific environments and using specific plugins.
* fixes [skip ci]
* Enable babel for tests
This enables babel for tests by using a mocha compiler
It uses the babel config from package.json
Transformed OptionsManager test to es2015 to see if it works
Removed the 5s timeout from cli tests, as the default timeout is already 10s, this should probably fix the timouts on travis that we had in babylon
Also run the cli tests on travis, they were disabled if istanbul active, but istanbul is always active on travis so we were never running this tests.
* ignore scripts directory
* only register for tests
* Set only flag correctly
* fix(shouldIgnore): filename normalization should be platform sensitive
shouldIgnore normalizes the path of the filename prior to running any "only" regexes or functions. The normalization uses "slash", which has some undesirable special cases for non-ASCII characters and longer paths. Changing the normalization behavior to always replace path separators.
There is no real need to add additional tests, because the tests are not run in an environment where path.sep !== '/'.
* Minor style fix to use double quotes.
* Remove conditional for regex replace to keep consistent behavior.
* whitespace [skip ci]
Use the data from https://github.com/kangax/compat-table to build the
browser data.
Each Babel plugin is mapped to a list of features in the compatibility
table (in `data/pluginFeatures.js`), and the minimum supporting
version looked up from the compatibility test data. The script builds
the final browser data file in `data/plugins.json`.
