3495f86c45
* get coverage for console functional test * instrument kibana * collect coverage stats after each test, on url navigation, refresh and back * switch to babel-plugin-istanbul * switch to babel-plugin-istanbul * [coverage service] basic version * trigger final coverage flush when ftr finishes, wait for all logs before exiting * add coverage report generation * increase optimizer timeout, re-run idx/babel plugin before istanbul * increase memory usage for node * put istanbul preset in the beginning to run as the last one * bump babel-plugin-istanbul up to 5.2.0 * cleanup * save unique json files with coverage * [functional test coverage] update coverage.json path * run code coverage on CI * increase max-old-space-size with env variable * fix coverage folder creation * use env variable to configure code coverage * revert ci config changes * remove duplicate plugin * remove comments * fixes |
||
|---|---|---|
| .. | ||
| common_babel_parser_options.js | ||
| common_preset.js | ||
| istanbul_preset.js | ||
| node_preset.js | ||
| package.json | ||
| README.md | ||
| webpack_preset.js | ||
@kbn/babel-preset
This package contains the shared bits of babel config that we use for transpiling our source code to code compatible with Node.JS and the various browsers we support.
usage
To use our presets add the following to the devDependencies section of your package.json:
"@kbn/babel-preset": "1.0.0",
Then run yarn kbn bootstrap to properly link the package into your plugin/package.
Finally, add either @kbn/babel-preset/node_preset or @kbn/babel-preset/webpack_preset to your babel config.
@kbn/babel-preset/node_preset is usually placed in a babel.config.js file.
@kbn/babel-preset/webpack_preset is usually placed directly in your webpack configuration.
NOTE: If you're transpiling code that will be run in both the browser and node you must transpile your code twice, once for each target. Take a look at the build tasks for @kbn/i18n to see how that can look.