nighthawk

> Anybody can write some HTML with some anchor tags and tie it to some routes declared in a server-side routing file. The back button will work. History will work. Refresh will work. Copy-and-pasting the URL into an email will work. It's so easy that even I can do it. The solution I use[1], and disclaimer also wrote, was targeted directly at server rendered SPA's to follow closely with these ideals. Layers over native anchor tags, just barebones handles the link clicking and uses Express routing which is obviously back end compatible. [1] https://github.com/wesleytodd/nighthawk

I'm seeing mention of https://ui-router.github.io/tutorial/react/helloworld and https://github.com/wesleytodd/nighthawk does anyone have experience with https://github.com/router5/router5/ ?

https://github.com/wesleytodd/nighthawk My team uses this, we built it in response to most of us not liking the React Router methodology, and already using Express, it seemed like a good route.

https://github.com/wesleytodd/nighthawk ^^ This is the one we developed on my team. No view coupling, uses industry standard underlying components (Express Router), and layers on top of existing applications seamlessly (aka, no view tie in points, just anchor tags).

We did something similar that uses the Express router: https://github.com/wesleytodd/nighthawk The one thing we didn't do was layer on top of a flux solution. Seemed more future proof to not tie to anything other than a routing style. If you wanted to do that with our solution it would be as simple as writing an action to do the url change.

My team uses this: https://github.com/wesleytodd/nighthawk Basically it is just the Express router wrapped with logic from Page.js for catching link clicks and what not. We do universal rendering with a simple middleware and share all our middleware, rendering and route definitions on both the FE and BE.

If you are interested, this is what my team uses and it works REALLY well for us. It uses the standalone Express 5.0 router, so any pattern that works in Express works here. https://github.com/wesleytodd/nighthawk

This is one of the major reasons I try to stick with more well established libraries when I can. For example, when choosing our teams universal routing solution, I used the Express router instead of going with the NEW SHINY react router. Of course this did mean wrapping it for use on the FE, but that was as easy as copying code form Page.js (another old school project). https://github.com/wesleytodd/nighthawk