You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, ReactLynx already has partial support for TanStack Router (previous X), including MemoryHistory and File-Based Routing as documented on our website. 🎉
--
That said, relying on the React web adapter isn't ideal in the long run. This setup works mainly because ReactLynx is partially compatible with React 18 APIs via preact/compat, which allows us to reuse the existing React adapter to a certain extent.
We’d love to think long-term and explore a better path going forward.
Would collaborating on a dedicated adapter make sense?
Cross-platform constraints
Lynx is a cross-platform framework with its largest user base targeting native mobile environments, and growing usages on our first-class Web and Desktop (not open sourced yet) support. Consequently"
Not every Web-centric feature is a good fit (e.g. SSR, URL assumptions).
Some Web APIs (e.g. document) are currently missing in Lynx (though adding subsets of these may make sense).
More importantly, native mobile navigation is very different. TikTok have an internal, scheme-based navigation system (which we plan to open source), but current lack a declarative routing layer on top. I believe this is a really interesting collaborative area.
Since we both embrace a "framework-agnostic core philosophy", there may be even more potentials for synergy.
I'd love to hear thoughts from the maintainers and the community!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, It's Xuan from Lynxjs.
I'm opening this discussion to explore what both teams could do to make Lynx and TanStack (Router) work better together
Current Status
Earlier this yr, when we open sourced Lynx, @tannerlinsley kindly posted about this:
Today, ReactLynx already has partial support for TanStack Router (previous X), including MemoryHistory and File-Based Routing as documented on our website. 🎉
--
That said, relying on the React web adapter isn't ideal in the long run. This setup works mainly because ReactLynx is partially compatible with React 18 APIs via
preact/compat, which allows us to reuse the existing React adapter to a certain extent.We’d love to think long-term and explore a better path going forward.
ReactLynx as a distinct framework
ReactLynx takes a multi-threaded approach to UI concurrency, with features such as Main Thread Scripting and more recently, Main Thread Component. We currently have no plan to pursue React 19 concurrent semantics.
From TanStack Router’s perspective, this raises a few questions:
Cross-platform constraints
Lynx is a cross-platform framework with its largest user base targeting native mobile environments, and growing usages on our first-class Web and Desktop (not open sourced yet) support. Consequently"
document) are currently missing in Lynx (though adding subsets of these may make sense).Since we both embrace a "framework-agnostic core philosophy", there may be even more potentials for synergy.
I'd love to hear thoughts from the maintainers and the community!
Beta Was this translation helpful? Give feedback.
All reactions