5ac8951ed9
## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [x] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. ## Documentation / Examples - [x] Make sure the linting passes
61 lines
1.8 KiB
Markdown
61 lines
1.8 KiB
Markdown
---
|
|
description: Extend the babel preset added by Next.js with your own configs.
|
|
---
|
|
|
|
# Customizing Babel Config
|
|
|
|
<details>
|
|
<summary><b>Examples</b></summary>
|
|
<ul>
|
|
<li><a href="https://github.com/vercel/next.js/tree/canary/examples/with-custom-babel-config">Customizing babel configuration</a></li>
|
|
</ul>
|
|
</details>
|
|
|
|
Next.js includes the `next/babel` preset to your app, which includes everything needed to compile React applications and server-side code. But if you want to extend the default Babel configs, it's also possible.
|
|
|
|
To start, you only need to define a `.babelrc` file (or `babel.config.js`) at the top of your app. If such a file is found, it will be considered as the _source of truth_, and therefore it needs to define what Next.js needs as well, which is the `next/babel` preset.
|
|
|
|
Here's an example `.babelrc` file:
|
|
|
|
```json
|
|
{
|
|
"presets": ["next/babel"],
|
|
"plugins": []
|
|
}
|
|
```
|
|
|
|
You can [take a look at this file](https://github.com/vercel/next.js/blob/canary/packages/next/build/babel/preset.ts) to learn about the presets included by `next/babel`.
|
|
|
|
To add presets/plugins **without configuring them**, you can do it this way:
|
|
|
|
```json
|
|
{
|
|
"presets": ["next/babel"],
|
|
"plugins": ["@babel/plugin-proposal-do-expressions"]
|
|
}
|
|
```
|
|
|
|
To add presets/plugins **with custom configuration**, do it on the `next/babel` preset like so:
|
|
|
|
```json
|
|
{
|
|
"presets": [
|
|
[
|
|
"next/babel",
|
|
{
|
|
"preset-env": {},
|
|
"transform-runtime": {},
|
|
"styled-jsx": {},
|
|
"class-properties": {}
|
|
}
|
|
]
|
|
],
|
|
"plugins": []
|
|
}
|
|
```
|
|
|
|
To learn more about the available options for each config, visit their documentation site.
|
|
|
|
> Next.js uses the **current** Node.js version for server-side compilations.
|
|
|
|
> The `modules` option on `"preset-env"` should be kept to `false`, otherwise webpack code splitting is turned off.
|