Replace old extract-errors script with new one Deletes the old extract-errors in favor of extract-errors2

Replace old extract-errors script with new one Deletes the old extract-errors in favor of extract-errors2

Replace old extract-errors script with new one Deletes the old extract-errors in favor of extract-errors2

Replace old extract-errors script with new one Deletes the old extract-errors in favor of extract-errors2

Replace old extract-errors script with new one Deletes the old extract-errors in favor of extract-errors2

Disable error minification in more bundles Not worth it because the number of errors does not outweight the size of the formatProdErrorMessage runtime.

Disable error minification in more bundles Not worth it because the number of errors does not outweight the size of the formatProdErrorMessage runtime.

Disable error minification in more bundles Not worth it because the number of errors does not outweight the size of the formatProdErrorMessage runtime.

Disable error minification in more bundles Not worth it because the number of errors does not outweight the size of the formatProdErrorMessage runtime.

Disable error minification in react-noop-renderer These aren't user facing, so there's no reason to add these messages to the error code map.

Update codes.json with extract-errors2 These new messages are ones that we opted out of minifying with ESLint, but appear in builds are configured to have minified errors in our Rollup config. We probably don't want to land all of these.

Alternate extract-errors that scrapes artifacts The build script outputs a special FIXME comment when it fails to minify an error message. CI will detect these comments and fail the workflow. The comments also include the expected error message. So I...

Alternate extract-errors that scrapes artifacts The build script outputs a special FIXME comment when it fails to minify an error message. CI will detect these comments and fail the workflow. The comments also include the expected error message. So I...

Alternate extract-errors that scrapes artifacts The build script outputs a special FIXME comment when it fails to minify an error message. CI will detect these comments and fail the workflow. The comments also include the expected error message. So I...

Alternate extract-errors that scrapes artifacts The build script outputs a special FIXME comment when it fails to minify an error message. CI will detect these comments and fail the workflow. The comments also include the expected error message. So I...

Add ! to FIXME comment so Closure doesn't strip it Don't love this solution because Closure could change this heuristic, or we could switch to a differnt compiler that doesn't support it. But it works. Could add a bundle that contains an unminified e...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Add ! to FIXME comment so Closure doesn't strip it Don't love this solution because Closure could change this heuristic, or we could switch to a differnt compiler that doesn't support it. But it works. Could add a bundle that contains an unminified e...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Don't run error transform in development We used to run the error transform in both production and development, because in development it was used to convert `invariant` calls into throw statements. Now that don't use `invariant` anymore, we only hav...

Output FIXME during build for unminified errors The invariant Babel transform used to output a FIXME comment if it could not find a matching error code. This could happen if there were a configuration mistake that caused an unminified message to slip ...

Output FIXME during build for unminified errors The invariant Babel transform used to output a FIXME comment if it could not find a matching error code. This could happen if there were a configuration mistake that caused an unminified message to slip ...