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.
Warnings are printed when testing an Ink component
See original GitHub issueWarning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
Warning: Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.
According to @vadimdemedes:
It’s from React actually. I don’t know how to make it forget about previous Ink reconciler instances. Because in tests you create a new Ink instance in every test, which creates a new React reconciler instance. And React apparently keeps track of context providers, but this conflict happens. Even if tests are run serially, it still complains. I tried unmounting between tests, but didn’t help. I don’t know how to clean up its cache or whatever to make React forget that this context was used before.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Update: tried reproducing it with react-dom and I couldn’t get the same warning message, however I did confirm that React isn’t clearing
_currentRendererof the context. This led to another interesting discovery - react-dom doesn’t create a new reconciler instance for each container node (separate app), like Ink does. Instead, react-dom implementsgetRootHostContextreconciler method, which allows to use one reconciler for multiple containers (apps). I assume if Ink implemented it the same way, this warning would disappear. I will get on it this week.Submitted https://github.com/vadimdemedes/ink/pull/170 to fix this. I would appreciate if anyone tried it out with their Ink apps to see if there are any regressions, thanks!