1ff7f07875
### What? BREAKING CHANGE: Bump the minimum required Node.js version. ### Why? Node.js 16 has reached end-of-life in September. Bumped to `18.18.2` since it contained some security-related patches: https://nodejs.org/en/blog/vulnerability/october-2023-security-releases ### How? Bumped `engines` where needed, upgraded the workflows. This will allow us to remove quite a few polyfills, I'll open separate PRs for those.
66 lines
3 KiB
Text
66 lines
3 KiB
Text
---
|
||
title: Supported Browsers
|
||
description: Browser support and which JavaScript features are supported by Next.js.
|
||
---
|
||
|
||
Next.js supports **modern browsers** with zero configuration.
|
||
|
||
- Chrome 64+
|
||
- Edge 79+
|
||
- Firefox 67+
|
||
- Opera 51+
|
||
- Safari 12+
|
||
|
||
## Browserslist
|
||
|
||
If you would like to target specific browsers or features, Next.js supports [Browserslist](https://browsersl.ist) configuration in your `package.json` file. Next.js uses the following Browserslist configuration by default:
|
||
|
||
```json filename="package.json"
|
||
{
|
||
"browserslist": [
|
||
"chrome 64",
|
||
"edge 79",
|
||
"firefox 67",
|
||
"opera 51",
|
||
"safari 12"
|
||
]
|
||
}
|
||
```
|
||
|
||
## Polyfills
|
||
|
||
We inject [widely used polyfills](https://github.com/vercel/next.js/blob/canary/packages/next-polyfill-nomodule/src/index.js), including:
|
||
|
||
- [**fetch()**](https://developer.mozilla.org/docs/Web/API/Fetch_API) — Replacing: `whatwg-fetch` and `unfetch`.
|
||
- [**URL**](https://developer.mozilla.org/docs/Web/API/URL) — Replacing: the [`url` package (Node.js API)](https://nodejs.org/api/url.html).
|
||
- [**Object.assign()**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object/assign) — Replacing: `object-assign`, `object.assign`, and `core-js/object/assign`.
|
||
|
||
If any of your dependencies include these polyfills, they’ll be eliminated automatically from the production build to avoid duplication.
|
||
|
||
In addition, to reduce bundle size, Next.js will only load these polyfills for browsers that require them. The majority of the web traffic globally will not download these polyfills.
|
||
|
||
### Custom Polyfills
|
||
|
||
If your own code or any external npm dependencies require features not supported by your target browsers (such as IE 11), you need to add polyfills yourself.
|
||
|
||
In this case, you should add a top-level import for the **specific polyfill** you need in your [Custom `<App>`](/docs/pages/building-your-application/routing/custom-app) or the individual component.
|
||
|
||
## JavaScript Language Features
|
||
|
||
Next.js allows you to use the latest JavaScript features out of the box. In addition to [ES6 features](https://github.com/lukehoban/es6features), Next.js also supports:
|
||
|
||
- [Async/await](https://github.com/tc39/ecmascript-asyncawait) (ES2017)
|
||
- [Object Rest/Spread Properties](https://github.com/tc39/proposal-object-rest-spread) (ES2018)
|
||
- [Dynamic `import()`](https://github.com/tc39/proposal-dynamic-import) (ES2020)
|
||
- [Optional Chaining](https://github.com/tc39/proposal-optional-chaining) (ES2020)
|
||
- [Nullish Coalescing](https://github.com/tc39/proposal-nullish-coalescing) (ES2020)
|
||
- [Class Fields](https://github.com/tc39/proposal-class-fields) and [Static Properties](https://github.com/tc39/proposal-static-class-features) (part of stage 3 proposal)
|
||
- and more!
|
||
|
||
### TypeScript Features
|
||
|
||
Next.js has built-in TypeScript support. [Learn more here](/docs/pages/building-your-application/configuring/typescript).
|
||
|
||
### Customizing Babel Config (Advanced)
|
||
|
||
You can customize babel configuration. [Learn more here](/docs/pages/building-your-application/configuring/babel).
|