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

Add support for using .babelrc in the app root. #493

Merged
merged 7 commits into from
Dec 26, 2016

Conversation

arunoda
Copy link
Contributor

@arunoda arunoda commented Dec 23, 2016

Reverts #466
And allows to configure babel via the .babelrc file.

If there's no such file, we'll add our preset next/babel by default. If not we'll use the .babelrc file.
Most of the time, user need to add next/babel as a preset.

If we are taking this in, we could support ES2015 in the config.next.js as well.

@rauchg
Copy link
Member

rauchg commented Dec 23, 2016

Missing README explanation

@arunoda
Copy link
Contributor Author

arunoda commented Dec 23, 2016

@rauchg Oh! I forgot that :)

@arunoda
Copy link
Contributor Author

arunoda commented Dec 23, 2016

@rauchg done.

}
```

Although it's not required, you will need to add `next/babel` as a preset. That's the default preset we use for all Next.js apps.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so, we removed support for babel in next.config.js right? Otherwise, we also have to make a mention of that here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We removed that. Now there's no such option.

@rauchg
Copy link
Member

rauchg commented Dec 25, 2016

@arunoda needs re-base 🙏

@arunoda
Copy link
Contributor Author

arunoda commented Dec 25, 2016

@rauchg done.

@rauchg rauchg merged commit ac2a718 into vercel:master Dec 26, 2016
@arunoda arunoda deleted the babelrc-support branch December 26, 2016 18:15
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants