This repository has been archived by the owner on Apr 20, 2023. It is now read-only.
Fix issue with Node production environment and react-transition-group's PropTypes #21
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.
This is my fix to a known issue, described below.
react-transition-group's custom PropTypes are set to null if the Node env is set to "production." This causes an Internal Server Error in Next.js, "Cannot read property 'isRequired' of null."
To fix this, I simply mirrored the react-transition-group's code by nullifying the prop type
timeoutsShape
only ifprocess.env.NODE_ENV
is"production"
.With this fix, the PropType will still be applied in development and create the appropriate console errors.