Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Warning: Exception thrown by hook while handling onSetChildren: Invariant Violation: Item must have been set
See original GitHub issue
How to reproduce:
- Check out the branch
modal npm run install && npm run start- Navigate to the modal functional examples.
- Open and close a modal example.
- Navigate to another page. You should see this warning in the console:
Warning: Exception thrown by hook while handling onSetChildren: Invariant Violation: Item must have been set
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
React Redux - Exception thrown by hook while handling ...
I'm having a strange error/warning at a reducer. If I set "stats" to the action's stats return value I get the error.
Read more >main.18b409e1.js.map - Google Git
node_modules/react-redux/es/utils/warning.js",". ... _hostParent ? false ? invariant(false, 'React DOM tree root should always have a node reference.
Read more >8 common React error messages and how to address them
Warning : Each child in a list should have a unique key prop; Prevent usage of Array index in keys; React Hook useXXX...
Read more >log.txt - Niagara Parks
But we need to wrap it in a try catch in case it is // wrapped in strict mode code which ... \'Exception...
Read more >reactstrap - UNPKG
lastSize;\n\n // Handle the item getting hidden as a result of our positioning without ... 'Exception thrown by hook while handling %s: %s',...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think we will go forward with this pull request expecting the update to react 16.x to fix the issue: https://github.com/cerner/terra-core/pull/224
We tried out the example above using react 16.0.0-alpha.11. We could not reproduce the issue with react 16.0.0-alpha.11.