babel-preset-kyt-core

babel-preset-kyt-core

An opinionated Babel preset, best used with kyt. Check out the Options for how to extend polyfill your build targets.

This preset is used as a default if a kyt project does not include a .babelrc It is also included as part of babel-preset-kyt-react

To install:

1. npm install babel-preset-kyt-core --save
2. In babelrc:

   {
     presets: [
       "babel-preset-kyt-core"
     ]
   }
   

Options

(see documentation for Babel preset options)

• envOptions (Object) - extend the default babel-preset-env options. The type of options, client, server, and test, are dependent on the value of process.env.KYT_ENV_TYPE which, when undefined, defaults to client. kyt will automatically set the KYT_ENV_TYPE when it runs commands. For debugging purposes, use "debug": true to see what the plugin is targeting. The following are the default babel-preset-env configurations used by kyt-core:

  • client

    modules: false,
    useBuiltIns: true,
    targets: {
      uglify: true,
      browsers: ['>1%', 'last 4 versions', 'not ie < 11'],
    },
    

  • server

    modules: false,
    useBuiltIns: true,
    targets: {
      node: 'current'
    },
    

  These are sensible defaults that work well with kyt out of the box. The client option, typically reserved for client builds in kyt, is used to target browsers, while the server option targets the current version of node. The client.targets.browsers configuration is in the browserlist format. The following is an example of how to override the option types in your babelrc configuration:

  {
    "presets": [
      [
        "babel-preset-kyt-core", {
          "envOptions": {
            "client": {
              "debug": true,
              "targets": {
                "browsers": ["last 2 versions"]
              }
            },
            "server": {
              "debug": true,
              "modules": true
            },
          },
        },
      ],
    ],
  }
  

  You can find additional options to configure babel-preset-env here.

• includeRuntime (Boolean) - whether or not to include babel-plugin-transform-runtime; default: false

Polyfilling

By default babel-preset-env, an internal dependency, is configured to useBuiltIns which means that you can install babel-polyfill as a dependency in your project and import 'babel-polyfill' at the top of your entry file (in a kyt project that would be src/client/index.js and src/server/index.js) to include an optimized polyfill for your build.

CHANGELOG

0.3.0 - XX/XX/XX

• Adds babel-preset-env, removes babel-preset-latest

0.2.0 - 03/23/17

• Includes babel-plugin-syntax-dynamic-import to allow parsing of dynamic import().

Changelog

0.3.0 (October 25, 2016)

BREAKING CHANGES

• Upgrades Jest to version 16 #259 See Jest docs for information on latest updates.

• Upgrades Webpack to v2.1.0-beta.25 #264 Check the recipes to see the latest syntax for common extensions. Additional info in Webpack's migration guide

FEATURES

• Adds serverless option to kyt #174 See the new static starter-kyt

• Flags can now be passed through to internal tools #230

• Adds multiple server entry handling #247

• Default starter-kyt on setup is now the universal starter-kyt #265

• Assets now use chunkhash #239

• Make logs more readable #190

• Displays Gzip size of assets #244

• Adds end to end tests #241