Meta tags:
description=Supported Browsers;

Headings (most frequently used words):

supported, browsers, features, and, language, configuring,

Text of the page (most frequently used words):
the (20), browsers (16), #supported (10), features (10), and (10), you (8), this (7), that (7), browserslist (6), react (5), your (5), polyfills (5), for (5), development (5), production (5), support (5), app (5), language (4), last (4), when (4), not (4), will (4), project (4), github (3), started (3), package (3), json (3), are (3), version (3), with (3), use (3), default (3), proposal (3), supports (3), create (3), facebook (2), learn (2), get (2), docs (2), configuring (2), updating (2), new (2), releases (2), available (2), scripts (2), page (2), change (2), folder (2), note (2), still (2), need (2), polyfill (2), see (2), based (2), all (2), here (2), specified (2), configuration (2), javascript (2), code (2), list (2), used (2), build (2), running (2), script (2), generated (2), includes (2), usage (2), modern (2), using (2), such (2), async (2), await (2), any (2), es6 (2), proposals (2), these (2), more (2), stage (2), properties (2), getting (2), copyright, 2025, inc, social, contributor, covenant, twitter, discussions, stack, overflow, community, next, previous, updated, dan, abramov, 2021, edit, editing, config, may, notice, changes, don, picked, right, away, due, detecting, quick, solution, delete, try, again, node_modules, cache, issue, babel, loader, does, include, automatically, above, needed, supporting, copy, safari, firefox, chrome, op_mini, dead, example, controls, outputted, emitted, compatible, creating, can, configured, https, browserl, ist, start, file, target, broad, range, global, builds, gives, good, experience, especially, but, provides, high, compatibility, many, other, make, sure, targeting, already, them, including, appropriate, manually, symbol, array, from, runtime, while, recommend, experimental, some, caution, heavily, uses, product, intend, provide, future, codemods, about, different, stages, typescript, flow, jsx, part, class, fields, static, dynamic, import, es2018, object, rest, spread, es2017, es2016, exponentiation, operator, superset, latest, standard, addition, syntax, also, internet, explorer, requires, set, older, advanced, deployment, back, end, integration, testing, building, styles, assets, structure, welcome, search, help, deprecated, read, skip, main, content,

Text of the page (random words):
supported browsers and features create react app skip to main content create react app is deprecated read more here create react app docs help github search k welcome getting started getting started folder structure available scripts supported browsers and features updating to new releases development styles and assets building your app testing back end integration deployment advanced usage support on this page supported browsers and features supported browsers by default the generated project supports all modern browsers support for internet explorer 9 10 and 11 requires polyfills for a set of polyfills to support older browsers use react app polyfill supported language features this project supports a superset of the latest javascript standard in addition to es6 syntax features it also supports exponentiation operator es2016 async await es2017 object rest spread properties es2018 dynamic import stage 4 proposal class fields and static properties part of stage 3 proposal jsx flow and typescript learn more about different proposal stages while we recommend using experimental proposals with some caution facebook heavily uses these features in the product code so we intend to provide codemods if any of these proposals change in the future note that this project includes no polyfills by default if you use any other es6 features that need runtime support such as array from or symbol make sure you are including the appropriate polyfills manually or that the browsers you are targeting already support them configuring supported browsers by default the generated project includes a browserslist configuration in your package json file to target a broad range of browsers based on global usage 0 2 for production builds and modern browsers for development this gives a good development experience especially when using language features such as async await but still provides high compatibility with many browsers in production the browserslist configuration controls the outputted javascript so that the emitted code will be compatible with the browsers specified the production list will be used when creating a production build by running the build script and the development list will be used when running the start script you can use https browserl ist to see the browsers supported by your configured browserslist here is an example browserslist that is specified in package json browserslist production 0 2 not dead not op_mini all development last 1 chrome version last 1 firefox version last 1 safari version copy note that this does not include polyfills automatically for you you will still need to polyfill language features see above as needed based on the browsers you are supporting when editing the browserslist config you may notice that your changes don t get picked up right away this is due to an issue in babel loader not detecting the change in your package json a quick solution is to delete the node_modules cache folder and try again edit this page last updated on 7 7 2021 by dan abramov previous available scripts next updating to new releases supported browsers supported language features configuring supported browsers docs get started learn react community stack overflow github discussions twitter contributor covenant social github copyright 2025 facebook inc