react

mirror of https://github.com/zebrajr/react.git synced 2026-01-15 12:15:22 +00:00

Files

Flarnie Marchan 8e4654015a Update error codes and results.json (#10619 )

* Update results.json

**what is the change?:**
Ran the build after updating Yarn lockfile and recorded latest build
size results.

**why make this change?:**
Let's get an idea of bundle size at this point, when we are preparing
the 16.0 RC.

**test plan:**
NA

**issue:**
https://github.com/facebook/react/issues/8854

* Update error codes

https://github.com/facebook/react/tree/master/scripts/release-manager#update-the-error-codes

2017-09-06 11:11:19 -07:00

__tests__

FB bundles wrap warning() calls in __DEV__ (#10314 )

2017-08-02 14:14:26 -07:00

codes.json

Update error codes and results.json (#10619 )

2017-09-06 11:11:19 -07:00

extract-errors.js

Fix error-codes not updating correctly (#10348 )

2017-08-02 10:38:27 +01:00

invertObject.js

Convert current build system to Rollup and adopt flat bundles (#9327 )

2017-04-05 16:47:29 +01:00

README.md

FB bundles wrap warning() calls in __DEV__ (#10314 )

2017-08-02 14:14:26 -07:00

replace-invariant-error-codes.js

FB bundles wrap warning() calls in __DEV__ (#10314 )

2017-08-02 14:14:26 -07:00

Types.js

Convert current build system to Rollup and adopt flat bundles (#9327 )

2017-04-05 16:47:29 +01:00

README.md

The error code system substitutes React's invariant error messages with error IDs to provide a better debugging support in production. Check out the blog post here.

Note for cutting a new React release

For each release, we run yarn build -- --extract-errors to update the error codes before calling yarn build. The build step uses codes.json for a production (minified) build; there should be no warning like Error message "foo" cannot be found for a successful release.
The updated codes.json file should be synced back to the master branch. The error decoder page in our documentation site uses codes.json from master; if the json file has been updated, the docs site should also be rebuilt (rake copy_error_codes is included in the default rake release task).
Be certain to run yarn build -- --extract-errors directly in the release branch (if not master) to ensure the correct error codes are generated. These error messages might be changed/removed before cutting a new release, and we don't want to add intermediate/temporary error messages to codes.json. However, if a PR changes an existing error message and there's a specific production test (which is rare), it's ok to update codes.json for that. Please use yarn build -- --extract-errors and don't edit the file manually.

Structure

The error code system consists of 5 parts:

codes.json contains the mapping from IDs to error messages. This file is generated by the Gulp plugin and is used by both the Babel plugin and the error decoder page in our documentation. This file is append-only, which means an existing code in the file will never be changed/removed.
extract-errors.js is an node script that traverses our codebase and updates codes.json. Use it by calling yarn build -- --extract-errors.
replace-invariant-error-codes.js is a Babel pass that rewrites error messages to IDs for a production (minified) build.
reactProdInvariant.js is the replacement for invariant in production. This file gets imported by the Babel plugin and should not be used manually.
ErrorDecoderComponent is a React component that lives at https://facebook.github.io/react/docs/error-decoder.html. This page takes parameters like ?invariant=109&args[]=Foo and displays a corresponding error message. Our documentation site's Rakefile has a task (bundle exec rake copy_error_codes) for adding the latest codes.json to the error decoder page. This task is included in the default bundle exec rake release task.