Nuxt.js: Move from babel-preset-es2015 to babel-preset-env
Now when installing packages there is warning:
[1/4] Resolving packages...
warning nuxt > [email protected]: � Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
[2/4] Fetching packages...
Maybe switch from preset-es* to env?
Alex-Sokolov
All 7 comments
It's implemented in the next release, coming soon.
Atinux
on 2 Nov 2017
Is there any way we can force this switch now? I'm using Objection.js and I'm having an issue I don't think I can go around with if I don't use the following config:
"presets": [
["env", {
"targets": {
"node": "current"
}
}],
"stage-1"
],
How can I do so?
sergiocastrovale
on 14 Nov 2017
@Atinux , will it be possible to change the babel-preset-env options via nuxt.config.js?
Now I have different options for client/server(targets: ie:9/node:true) and can't configure their correct, because don't have context
atos1990
on 15 Nov 2017
Are you setting build.babel.presets key?
Atinux
on 15 Nov 2017
@Atinux , yes. How I can specify targets in this preset? This property different for client and server, but bundles for their build with the single command - 'nuxt build'. I don't now how dynamically change this property during assembly
atos1990
on 15 Nov 2017
I can specify different environments in .babelrc. But there is no possibility specify process.env.BABEL_ENV dynamically
atos1990
on 15 Nov 2017
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
![lock[bot] picture](https://avatars1.githubusercontent.com/in/6672?v=4&s=40)
lock[bot]
on 2 Nov 2018
Related issues
lazycrazy
·
3Comments
maicong
·
3Comments
msudgh
·
3Comments
vadimsg
·
3Comments
shyamchandranmec
·
3Comments
Most helpful comment
It's implemented in the next release, coming soon.