kibana/packages/kbn-babel-preset
Joe Portner 13593344a0
Add lockfile symlinks (#55440)
This is to enable dependency scanning tools to correctly resolve
the dependencies in each package.json file that is used in
production.
2020-01-27 11:38:20 -05:00
..
common_babel_parser_options.js autofix all violations 2019-12-13 23:17:13 -07:00
common_preset.js Update babel-typescript config (#53108) 2019-12-16 19:28:54 +01:00
istanbul_preset.js autofix all violations 2019-12-13 23:17:13 -07:00
node_preset.js autofix all violations 2019-12-13 23:17:13 -07:00
package.json Revert "Update babel related packages (#52754)" 2019-12-17 11:32:49 -07:00
README.md [kbn/babel-preset] add readme (#39854) 2019-06-28 11:06:46 -07:00
webpack_preset.js Add babel-plugin-styled-components to webpack config (#52862) 2019-12-12 16:29:59 +01:00
yarn.lock Add lockfile symlinks (#55440) 2020-01-27 11:38:20 -05:00

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