<p dir="auto">We are investigating using React for drawing custom native UIs (that fall outside the scope of react-native and react-windows-native). <code class="notranslate">ReactFiberReconciler</code> seems like the most sensible place to start (assuming fibers start getting used in mainline relatively soon, which seems reasonably likely), and it certainly seems to be very easy to get a proof of concept up and running using it, at least so far.</p>
<p dir="auto">If not this, then what is the recommended entry point for 3rd party renders to use?</p>
<p dir="auto">This issue is intended to be a discussion for how to distribute the ReactFiberReconciler.js file and dependencies for custom renderers.</p>
<p dir="auto">Currently first-class renderers within the React codebase/Facebook ecosystem do not have any concerns for this because of Haste / access to the React.js build + publish tooling within this codebase.</p>
<p dir="auto">3rd party renderers are currently adding <code class="notranslate">react-dom</code> to their dependency list and requiring <code class="notranslate">react-dom/lib/ReactFiberReconciler.js</code> to build and expose their custom renderer.</p>
<p dir="auto">Ideally, <code class="notranslate">ReactFiberReconciler.js</code> would be distributed with the <code class="notranslate">react</code> package or as a standalone <code class="notranslate">react-fiber-reconciler</code> package. Whether this is at <code class="notranslate">react/reconciler.js</code> or <code class="notranslate">react/lib/reconciler.js</code> idk. I think at the root is better to continue the discouragement of looking in <code class="notranslate">react/lib/*</code> for anything.</p>
<p dir="auto">I understand flat bundles are coming, too. I don’t know if that should block this or if this could be a flat bundle, or any other alternative.</p>
<p dir="auto">Is this something the team is ready to commit to and support if we came to a decision on approach and I put together a PR?</p>
<p dir="auto">Related issues:</p>
<ul dir="auto">
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="155564701" data-permission-text="Title is private" data-url="https://github.com/facebook/react/issues/6795" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/6795/hovercard" href="https://github.com/facebook/react/issues/6795">#6795</a> Create Separate Copies of Each Renderer</li>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="117001444" data-permission-text="Title is private" data-url="https://github.com/facebook/react/issues/5472" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/5472/hovercard" href="https://github.com/facebook/react/issues/5472">#5472</a> Include flow type definitions (flow type distribution proposal at <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="117001444" data-permission-text="Title is private" data-url="https://github.com/facebook/react/issues/5472" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/5472/hovercard?comment_id=282394248&amp;comment_type=issue_comment" href="https://github.com/facebook/react/issues/5472#issuecomment-282394248">#5472 (comment)</a>)</li>
</ul>
<ul dir="auto">
<li><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/sebmarkbage/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/sebmarkbage">@sebmarkbage</a> <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/spicyj/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/spicyj">@spicyj</a></li>
</ul>