Skip to content
This repository has been archived by the owner on May 11, 2018. It is now read-only.

Releases: babel/babel-preset-env

v1.1.9

24 Feb 16:54
Compare
Choose a tag to compare

v1.1.9 (2017-02-24)

🐛 Bug Fix

Since we've (mostly @yavorsky) have fixed a number of bugs recently with the debug option output, we added the ability to assert stdout matches what we expect. Read the updated CONTRIBUTING.md for more info.

This fixes a bug in the debug output where incorrect target(s) were being displayed for why a particular plugin/preset was being included.

Given targets:

{
  "firefox": 52,
  "node": 7.4 
}

Before:

Using plugins:
  transform-es2015-destructuring {"node":6.5}
  transform-es2015-for-of {"node":6.5}
  transform-es2015-function-name {"node":6.5}
  transform-es2015-literals {"node":4}
  transform-exponentiation-operator {"firefox":52}
  syntax-trailing-function-commas {"firefox":52}

After:

Using plugins:
  transform-es2015-destructuring {"firefox":52}
  transform-es2015-for-of {"firefox":52}
  transform-es2015-function-name {"firefox":52}
  transform-es2015-literals {"firefox":52}
  transform-exponentiation-operator {"node":7.4}
  syntax-trailing-function-commas {"node":7.4}

📝 Documentation

🏠 Internal

v1.1.8

24 Feb 13:40
Compare
Choose a tag to compare

v1.1.8 (2017-01-10)

🐛 Bug Fix

Makes sure that all transformations on targets (such as exclude/include) are run before logging out with the debug option. Fixes (#127).

🏠 Internal

v1.1.7

24 Feb 13:39
Compare
Choose a tag to compare

v1.1.7 (2017-01-09)

Had a publishing issue in the previous release.

v1.1.6

06 Jan 22:35
Compare
Choose a tag to compare

v1.1.6 (2017-01-06)

🐛 Bug Fix

{
  "targets": {
    "browsers": ["ios >= 6"] // was resolving to {ios: 10} rather than {ios: 6}
  }
}

v1.1.5

04 Jan 17:52
Compare
Choose a tag to compare

v1.1.5 (2017-01-04)

🐛 Bug Fix

{
  "presets": [
    ["env", {
      "targets": {
        "chrome": "52", // will error since it's not a number,
        "chrome": 52 // correct!
      }
    }]
  ]
}

Now it prints the transformed targets/environments rather than the browsers query.

Using targets:
{
  "chrome": 53,
  "ie": 10,
  "node": 6
}

Modules transform: false

Using plugins:
  transform-es2015-arrow-functions {"chrome":47,"node":6}
  transform-es2015-block-scoped-functions {"chrome":41,"ie":11,"node":4}

Using polyfills:
  es6.typed.uint8-clamped-array {"chrome":5,"node":0.12}
  es6.map {"chrome":51,"node":6.5}

v1.1.4

16 Dec 23:07
Compare
Choose a tag to compare

v1.1.4 (2016-12-16)

v1.1.2-v1.1.4

🐛 Bug Fix

The new exclude/include options weren't working correctly for built-ins. (#102).

Also fixes an issue with debug option.

v1.1.1

13 Dec 23:28
Compare
Choose a tag to compare

v1.1.1 (2016-12-13)

🐛 Bug Fix

Regression with the previous release due to using Object.values (ES2017). This wasn't caught because we are using babel-register to run tests and includes polyfills so it didn't fail on CI even though we have Node 0.10 as an env. Looking into fixing this to prevent future issues.

v1.1.0

13 Dec 23:01
Compare
Choose a tag to compare

v1.1.0 (2016-12-13)

🚀 New Feature

  • Add exclude option, rename whitelist to include (#89) (@hzoo)

Example:

{
  "presets": [
    ["env", {
      "targets": {
        "browsers": ["last 2 versions", "safari >= 7"]
      },
      "include": ["transform-es2015-arrow-functions"],
      "exclude": [
        "transform-regenerator",
        "transform-async-to-generator",
        "map"
      ],
      "useBuiltIns": true
    }]
  ]
}

"exclude": ["transform-regenerator"] doesn't transform generators and removes regeneratorRuntime from being imported.

"exclude": ["transform-async-to-generator"] doesn't use the built-in async-to-gen transform so you can use something like fast-async.

"exclude": ["map"] doesn't include the Map polyfill if you know you aren't using it in your code (w/ useBuiltIns). (We will figure out a way to automatically do this #84).

If you pass a wrong plugin it will error: valid options for include/exclude are in /data/plugin-features.js and /data/built-in-features.js (without the es6.)

v1.0.2

10 Dec 16:41
Compare
Choose a tag to compare

v1.0.2 (2016-12-10)

🐛 Bug Fix

Was requiring the wrong module kinda of like in v1.0.1:

https://github.com/zloirock/core-js#ecmascript-6-symbol

-import "core-js/modules/es6.object.get-own-property-symbols";

The test is just a part of Symbol.

v1.0.1

10 Dec 15:20
Compare
Choose a tag to compare

v1.0.1 (2016-12-10)

🐛 Bug Fix

We were outputting an invalid path for regenerator!

+import "regenerator-runtime/runtime";
-import "core-js/modules/regenerator-runtime/runtime"-