@vevo/babel-config-vevo

babel-config-vevo

GOCD Pipeline

Installation/Updating

babel requires a couple of core libraries to be installed seperately in each project's directory, so you'll have to run a little script to install the correct versions of the packages required.

# Installation and Update script for peer deps
(
  export PKG=@vevo/babel-config-vevo;
  yarn add --dev $PKG@latest;
  npm info "$PKG@latest" peerDependencies --json | command sed 's/[\{\},]//g ; s/: /@/g' | xargs yarn add --dev "$PKG@latest"
)

make a config file: .babelrc:

If you're building from the command line, you might also need to run yarn add @babel/cli

Browser Config

{
  "presets": [
    "module:@vevo/babel-config-vevo",
    [
      "@babel/preset-env",
      {
        targets: "> 5%"
      }
    ],
  ]
}

Node Config

{
  "presets": [
    "module:@vevo/babel-config-vevo",
    [
      "@babel/preset-env",
      {
        targets: {
          "node": true
        }
      }
    ],
  ]
}

Updating Babel

First change the package.json peer dependency versions to whatever the newest versions of babel are.

You may also be able to delete some plugins if they have transitioned into stage 4.

Then you will need to rerun the script mentioned above in each repo that needs the update.

Updating Babel in Mesa

Mesa handles all of the preset-env configuration. So you will need to update the peer deps and this package in mesa directly. Each individual mesa app then just needs to update mesa.