Configuring Browser Support

The official Nx plugins rely on browserslist for configuring application browser support. This affects builds, both production and development, and will decide on which transformations will be run on the code when built.

In general, the more modern your applications browser support is, the smaller the filesize as the code can rely on modern API's being present and not have to ship polyfills or shimmed code.

By default, applications generated from official Nx generators ship an aggressively modern browser support config, in the form of a .browserslistrc file in the root of the application with the following contents.

This configuration is used for many tools including babel, autoprefixer, postcss, and more to decide which transforms are necessary on the source code when producing built code to run in the browser.

Adding Support for IE 11

Adding support for IE or any other browser is as easy as changing the .browserslistrc file, following the rules and options listed on the browserslist documentation. These changes will affect differential loading and how the code is processed through babel and other tools for producing your builds.

To add support for IE 11 simply change the final line in the .browserslistrc file to include IE:

For additional information regarding the format and rule options, please see: https://github.com/browserslist/browserslist#queries

Debugging Browser Support

Sometimes broad configurations like > 0.5%, not IE 11 can lead to surprising results, due to supporting browsers like Opera Mini or Android UC browser.

To see what browsers your configuration is supporting, run npx browserslist in the application's directory to get an output of browsers and versions to support.

Alternatively, if your support config is short you can just add it as a string param on the CLI: