Echo JS 0.11.0

<~>

tracker1 9 days ago. link 1 point
Kind of cool to see this...  Definitely useful for  something like an editor/forms environment for near state.  Probably a bit harder to integrate with something like page navigation actions, especially with route changes... though can probably track/attach the state/step with route changes for better undo/back and forward tracking.
unadlib@gmail.com 3 days ago. link 1 point
Thanks for checking it out! I agree—editor and form flows are the sweet spot right now, but we’ve actually been experimenting with treating route transitions as explicit steps in the timeline. If you capture the route plus params alongside
  each state snapshot, you can drive undo/redo straight into navigation and even support back/forward replay. It’s still rough around the edges, yet we’re optimistic the model can stretch that far. If you have a specific router setup in mind,
  I’d love to see it and figure out what’s missing.
tracker1 2 days ago. link 1 point
Not really a good current example.  In the past I've done the redux integration with react-router and a few other bits... that got "interesting" to say the least.  So I know enough to know it's a pain to hard wire all of it up and get it working to trigger from/to the browser, redux, etc and having things sync right.

If I were building from scratch today, I'm somewhat inclined to look at tanstack router, not that I'd use all of tanstack.  React-Router itself has just been kind of a mess along the way.  It's been a couple years since I've been able to start a UI project from scratch instead of inheriting what's already in progress though.