Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

babel 7 ecmascript 7 configuration #9054

Closed
m-korkut opened this issue Nov 21, 2018 · 6 comments
Closed

babel 7 ecmascript 7 configuration #9054

m-korkut opened this issue Nov 21, 2018 · 6 comments
Labels
i: question outdated A closed issue/PR that is archived due to age. Recommended to make a new issue

Comments

@m-korkut
Copy link

m-korkut commented Nov 21, 2018

how use babel 7 version into ecmascript 7 configuration ?

example my -> .babelrc -->

{
"plugins":[
   //.....
               ],
  "presets": [
     "@babel/env",
     "@babel/flow",
    "@babel/preset-react"
                    ]
 }
@babel-bot
Copy link
Collaborator

Hey @m-korkut! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

@loganfsmyth
Copy link
Member

Could you clarify what you mean by "ecmascript 7 configuration"?

@m-korkut
Copy link
Author

how to ecmascript 7 configuration in the babelrc folder ?

@nicolo-ribaudo
Copy link
Member

If by "ECMAScript 7 configuration" you mean that you want to transform ECMAScript 7 (2016) to ECMAScript 5, your configuration is already ok.

@xtuc
Copy link
Member

xtuc commented Nov 22, 2018

This reminds me about #6613, it would be usefull for this kind of use-cases.

@nicolo-ribaudo
Copy link
Member

Closing as a duplicate of #6613. Targeting a specific ECMAScript version isn't supported yet.

@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Jun 26, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
i: question outdated A closed issue/PR that is archived due to age. Recommended to make a new issue
Projects
None yet
Development

No branches or pull requests

5 participants