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.
ReactMount - refactor to not rely on the DOM
See original GitHub issueAs seen here (https://github.com/facebook/react-native/blob/master/Libraries/ReactNative/ReactNativeMount.js#L86)
“As soon as ReactMount is refactored to not rely on the DOM, we can share code between the two. For now, we’ll hard code the ID logic.”
Is this still wanted? I’m working on a project where it would help if ReactMount was not dependant on the DOM as it has a different render target. I don’t mind taking a look at doing this, but I just want to check if it’s a wanted feature or whether in cases like mine I should just go about writing a completely new renderer.
I think it would be useful as it would make it easier to use React for projects which aren’t DOM related.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (2 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
We’re changing all internals and this will no longer be relevant after a while.
@sebmarkbage Okay thanks for clarifying that. So 0.14 for the time being will be dependant on the DOM then? It would be cool if the injection could be called somewhere else other than when the react package is loaded, maybe in the render function because then other renderers could inject their own plugins? (For now at least until it’s all done statically)