Resolve a route into something the navigation stack can display.
The resolving is not here: it is @stone-js/use-react-core, unchanged, and the same code the
web renderer calls. Which component answers, what its loader returns, how the layout wraps it
and how the head merges are the same questions with the same answers on both platforms, and a
page written for one needs no native variant of its logic.
What is here is the one line that differs. There is no HTML document to assemble and no markup
to hydrate, so the resolved tree becomes native content, and a middleware puts it on the stack.
Resolve a route into something the navigation stack can display.
The resolving is not here: it is
@stone-js/use-react-core, unchanged, and the same code the web renderer calls. Which component answers, what its loader returns, how the layout wraps it and how the head merges are the same questions with the same answers on both platforms, and a page written for one needs no native variant of its logic.What is here is the one line that differs. There is no HTML document to assemble and no markup to hydrate, so the resolved tree becomes native content, and a middleware puts it on the stack.