Browser support

Docusaurus allows sites to define the list of supported browsers through a browserslist configuration.

Purpose

Websites need to balance between backward compatibility and bundle size. As old browsers do not support modern APIs or syntax, more code is needed to implement the same functionality, penalizing all other users with increased site load time. As a tradeoff, the Docusaurus bundler only supports browser versions defined in the browser list.

The browser list by default is provided through the package.json file as a root browserslist field.

caution

On old browsers, the compiled output will use unsupported (too recent) JS syntax, causing React to fail to initialize and ending up with a static website with only HTML/CSS and no JS.

Default values

Websites initialized with the default classic template has the following in package.json:

package.json

{  "name": "docusaurus",  // ...  "browserslist": {    "production": [">0.5%", "not dead", "not op_mini all"],    "development": [      "last 1 chrome version",      "last 1 firefox version",      "last 1 safari version"    ]  }  // ...}

Explained in natural language, the browsers supported in production are those:

• With more than 0.5% of market share; and
• Has official support or updates in the past 24 months (the opposite of "dead"); and
• Is not Opera Mini.

And browsers used in development are:

• The latest version of Chrome or Firefox or Safari.

You can "evaluate" any config with the browserlist cli to obtain the actual list:

npx browserslist --env="production"

The output are all browsers supported in production. Below is the output in May, 2021:

and_chr 89and_uc 12.12chrome 89chrome 88chrome 87edge 89edge 88firefox 86ie 11ios_saf 14.0-14.5ios_saf 13.4-13.7safari 14safari 13.1samsung 13.0

Read more

You may wish to visit the browserslist documentation for more specifications, especially the accepted query values and best practices.