Download next.js/docs/03-architecture/supported-browsers.mdx from Devendra174/react-code-dataset: direct link, hf CLI and curl.
- Browser
- Download file 2.99 kB
-
https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/docs/03-architecture/supported-browsers.mdx
- Command line
-
hf download hf://datasets/Devendra174/react-code-dataset/next.js/docs/03-architecture/supported-browsers.mdx
-
curl -L -o supported-browsers.mdx https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/docs/03-architecture/supported-browsers.mdx
2.99 kB
| --- | |
| 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) (ES2022) | |
| - and more! | |
| ### TypeScript Features | |
| Next.js has built-in TypeScript support. [Learn more here](/docs/pages/api-reference/config/typescript). | |
| ### Customizing Babel Config (Advanced) | |
| You can customize babel configuration. [Learn more here](/docs/pages/guides/babel). | |