This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Add NODE_ENV=development
to test
script to see React errors
#2113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please be sure to read the contributor's guide to the GitHub package before submitting any pull requests.
Requirements
Description of the Change
This PR sets our
test
script to run withNODE_ENV=development
. Doing so helped us catch/debug a React issue as described in f60d186Rationale: React runs fewer checks in production mode for efficiency. For example, in development mode it checks that props have not been mutated but in production mode it seems that it does not. We had an issue where tests were failing on CI due to mutated props but not locally until we set the NODE_ENV to be development. Presumably our CI is running with development mode by default. Let's just have this always be the case to err on the side of catching more errors locally.
Screenshot/Gif
N/A
Alternate Designs
N/A
Benefits
Catch bugs more easily / faster!
Possible Drawbacks
None.
Applicable Issues
See f60d186
Metrics
N/A
Tests
N/A
Documentation
N/A
Release Notes
User Experience Research (Optional)
N/A