Files
react/packages/react-devtools-extensions/firefox
Brian Vaughn ee6a05c2bf Bumped DevTools Chrome and Firefox versions in Babel config (#21185)
We have been building DevTools to target Chrome 49 and Firefox 54. These are super old browser versions and they did not have full ES6 support, so the generated build is more bloated than it needs to be.

DevTools uses most modern language features. Off the top of my head, we it uses basically everything but async and generator functions.

Based on CanIUse charts– I believe that in order to avoid unnecessary polyfill/wrapper code being generated, we'd need to target Chrome 60+ (released 2017-07-25) and Firefox 55+ (released 2017-04-18). This seems like a reasonable set of browsers to target.

Note that we can't remove the IE 11 target from the react-devtools-core backend yet due to Hermes (React Native) ES6 support but that should be doable by the end of the year given current engineering targets. But we could update the frontend target, as well as the targets for the extensions and the react-devtools-inline package.

This commit increases the browser targets then for Chrome (from 49 to 60) and Firefox (from 54 to 55)
2021-04-06 11:18:46 -04:00
..
2019-08-13 15:59:43 -07:00

The Firefox extension

The source code for this extension has moved to shells/webextension.

Modify the source code there and then rebuild this extension by running node build from this directory or yarn run build:firefox from the root directory.

Testing in Firefox

  1. Build the extension: node build
  2. Follow the on-screen instructions.

You can test upcoming releases of Firefox by downloading the Beta or Nightly build from the Firefox releases page and then following the on-screen instructions after building.