maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
kibana/packages/kbn-babel-preset
History
Tim Roes bbb9421678
Make babel understand TypeScript 3.7 syntax (#50772) 
* Use correct babel plugins

* Make one change using new operator

* Fix i18n babel config
2019-11-15 18:29:25 +01:00
..
common_babel_parser_options.js Create vendor dll for the client modules (#22618) 2018-12-05 15:45:19 +00:00
common_preset.js Make babel understand TypeScript 3.7 syntax (#50772) 2019-11-15 18:29:25 +01:00
istanbul_preset.js Collecting code coverage from functional tests (#40512) 2019-10-10 07:56:49 +02:00
node_preset.js fix(NA): correctly reference babel plugin into the node babel preset (#50090) 2019-11-07 17:25:00 -05:00
package.json Make babel understand TypeScript 3.7 syntax (#50772) 2019-11-15 18:29:25 +01:00
README.md [kbn/babel-preset] add readme (#39854) 2019-06-28 11:06:46 -07:00
webpack_preset.js manually setup module transforms so to support async imports in webpack (#44413) 2019-08-29 14:04:12 -07:00

README.md

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