Closed achavez closed 6 years ago
Maybe we try something like:
$ npm install --save-dev babel-preset-env
presets: [
["env", {
"targets": {
"browsers": ["last 2 versions", "ie >= 10"]
}
}]
]
babel-preset-env
is implemented and will be in next release
So my understanding of Babel is that with the way we have it setup it should be transpiling all JS features that aren't widely supported, but that seems to not be happening with everything that we need to support IE11.
Example:
Looking at the code for
babel-preset-es2015
, it doesn't appear that transformation is applied: https://github.com/babel/babel/blob/master/packages/babel-preset-es2015/src/index.jsSo I'm wondering if we should consider a different transform. It looks like
Symbol
is ES2016 or ES6. Searching forbabel-preset-es2016
leads tobabel-preset-latest
which leads tobabel-preset-env
.So maybe we should use that?
cc @allanjamesvestal