New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential isRequired bug in v15.8.0 and above #376
Comments
Have you tried v15.8.1? #370 might be related. |
Also, what is "died in status LOADING_SOURCE_CODE" from? You can see here: https://npm.runkit.com/prop-types that |
Yes, we were on
I think that's part of our error boundary setup. |
I wonder if it’s some kind of bundle splitting or duplication issue. What is the value of PropTypes? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
ping @paulgpeterson, any update? |
We have been encountering the following error in our web app when using
v15.8.0
or higher. We are using a micro front end-style setup, so I haven't ruled out that it may just be something with our setup - but it works fine atv15.7.2
---At the given line, the component is using
func.isRequired
. We also have a usage ofstring.isRequired
, but it crashes at the first instance. Looking through the changelog entry for v15.8.0, I don't see anything relating to theisRequired
property.For now, we're reverting to an earlier version, but please let me know if you have any ideas for the more recent versions.
Thanks
The text was updated successfully, but these errors were encountered: