* Replace manual electron-to-chromium list and function with external library
* test fixtures for electron: Switch to electron 1.4, with known chrome version and update expected output
* update tests: electron 1.0 used chrome 49, not 50
* import only the relevant function from electron-to-chromium
* electron fixtures: Use number instead of string
* If both chrome and electron are defined, choose the lower version to preserve
* Add to test cases to verify correct handling of chrome number
browserslist queries, especially ones with percentages, often bring in mobile browsers that _probably_ have the similar support level as desktop ones, but since there's no support for them in the data, including them here would just lead to all plugins being enabled always.
It's also easy to get crazy things like `op_mini` or `and_uc` in the results.
Browserslist also reports iOS Safari as `ios_saf`, while the data uses `ios`, so it needs to be renamed.
* 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.
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`.